|
The 1956 LGP-30 computer, subject of hacker lore, is one of only 45 made in Europe. Remember to always visit your grandparents!
|
|
|
|
|
Today, Mark Zuckerberg announced that Meta will be firing more than 11,000 employees, which is about 13% of its total strength. I guess now it's more, "About-faceBook"?
Sorry for the employees and their families, but my heart wouldn't break if the company went bye-bye.
|
|
|
|
|
Kent Sharkey wrote: but my heart wouldn't break if the company went bye-bye. Maybe someone with an active (and not blocked) twitter account could suggest Musk to buy Meta once he is done with twitter?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
One thing that I was actually impressed with was (in an article I read yesterday somewhere) that people are getting 16 weeks paid + 2 weeks for each year they worked there, and 6 months of continued health care coverage. Not sure how that works for non-US employees, but if true, that at least struck me as an honorable way of letting people go.
|
|
|
|
|
In contrast, Musk's mass firing complies with the US WARN act (60 days) and California's equivalent (90 days) by providing a 90 day vacation with full pay and benefits to all the laid off employees while at the same time preventing them from sabotaging Twitter's systems. The lockout is to prevent violations of both US and California computer crime Laws.
I wonder if Zuckerburg considered sabotage of FB's systems when allowing these employees continued access to FB's systems.
|
|
|
|
|
He did. The article said all their accounts were restricted to only email access before they let the unfortunate employees know about it.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I'm betting they have to sign an NDA and an agreement not to badmouth Meta in any public forum to get and continue to receive that severance package.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
You are probably right.
Let's wait the time slot gets to the end. I think I will buy a new load of popcorn...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I don't care for Facebook, but the news of its demise is premature. They are still earning a lot of money...
|
|
|
|
|
‘Struth. But they do need to get Zuck to lose a bit of his metaverse drive.
TTFN - Kent
|
|
|
|
|
What I don't understand is the "I accept fully responsibility" said by Zuckeberg...
as that comment would bring any difference
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
The annual 'State of the Octoverse' report notes an increase in infrastructure-as-code adoption and the growing role of operations in open source development, among other trends. International Aeronautic Commission? Irish Albino Congress?
|
|
|
|
|
I am Croot?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
I cry
When socials deserve to DIIIIIIIIIIIIE
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Musk is Dave and Twitter is HAL.
All jokes aside, I really wonder how this fragility occurs. Bit are bits. What in the world is so complicated about Twitter than it can't be a reliable process? How is code written where this fragility is effectively engineered into the system?
|
|
|
|
|
|
Designing a system that has to be used concurrently by hundreds of thousands of users spanning the entire world is difficult, from managing the various CDNs to ensuring real time communication (when I post a tweet I want it visible to all Twitter users the second I post it, not minutes or hours later).
Add to that the various services that interact with system in ways it was not designed to accomodate (i.e. bots, TwitterDeck, third party apps).
Now enter politics: some countries ban it altogether, some other limit the content by provenience or keywords, in some other the platform is liable for the contents the users post, in other yet the government may want to access the user account at any given time. This requires continuously shoehorning in an already complex architecture everchanging modifications (because politicians never stop flapping their moronic mouths) that are vital to the continued existance of the system.
ADD: I forgot an important tidbit of information.
Twitter is old. Ages old. When it was born it had to accomodate the possibility of sending tweets via SMS (hence the previous 140 chars limit, SMS support 160 and 20 were reserved for the session ID) because smartphones didn't exist in any meaningful form, mobile Internet wasn't a thing and was often GPRS, expensive and WAP based. Many server technologies and frameworks didn't exist yet.
It has been updated, upgraded and patched for close to 15 years but the underlying architecture is still the same, with overhanging functionalities expanding it (i.e. pics on twitter, they were hell to implement and are basically implemented on the client side).
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I was thinking along similar lines - if Twitter's codebase is this poor, it's no wonder Twitter has a Bot and hijacked account problem. Musk bought possibly the largest bowl of spaghetti ever made.
|
|
|
|
|
obermd wrote: the largest bowl of spaghetti ever made.
Those are banking systems.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
At least banking systems have the excuse of being created before any sort of structured programming was conceived.
|
|
|
|
|
Thing is, it seems to be running just fine as of now.
If nobody dicks with the code (engineers), it should theoretically keep tweeting.
|
|
|
|
|
Ron Anders wrote: nobody dicks with the code I've heard fairytales about this concept.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
This is our first GA release to support Arm64. In addition some of the other prominent features it includes are .NET 7, enterprise support for setup including rollback, and much more The coincidence that this always launches the same time as a .NET version amazes me
|
|
|
|
|
C# opens some entirely new fronts, even while advancing several themes that have been in motion over past releases. .NET 7, C# 11... is this some kind of cross-promotion with 7-11? Can I get a Slurpee?
|
|
|
|