ultra pure water production itself is responsible for untold amounts of hydroflouric acid and ammonia , and most etching processes have an F-Gas involved, and most plants that do this work have tremendously high energy (power) costs due to stability needs/hvac.
The claim was that "the materials that go into a chip are nothing". Arguing that that is not that case does not really put someone on the hook to explain or even have any clue how to do it better.
They shorted me a day off credit on the first day of offering the 200+ subscription and it took me 6 weeks for a human to tell me "whoops well we'll fix that, cya."
I can't be alone . Literally the worst customer experience I've ever had with the most expensive personal dot com subscription I've ever paid for.
Never again. When Google sets the customer service bar there are MAJOR issues.
very few people can do the mental gymnastics required to equate " we look forward to realizing Vimeo’s full potential as we reach new heights together " to "you're all getting fired."
at some point in the now far-distant past CEOs used to make heartfelt speeches and memos to a soon-to-be-downsized staff about how hard decisions had to be made and blah-blah-blah; now it's more about sequestering the decision makers away from the damaged goods while projecting daisies and sunshine for would-be investors.
The game has shifted far from the human factor into a purely financial/investor loop. Good for some people but generally worse for people .
And before I hear it : Yes it was always about money, but business wasn't always about investors . That projection of liability to a remote party is exactly the issue.
Bending Spoon's business model has been -- at least for a decade -- buying companies that didn't operate profitably; stopping or slowing ongoing eng investments; and operating them profitably. Often that involves raising prices, but everyone is adults here.
Nobody lied. Vimeo will continue to operate, and probably will even have targeted ongoing development.
You can't point out the place where they promised the workers jobs. Because there was no such commitment, either before or after the sale.
The company failed. In 4 years, they managed to turn the valuation from $8.5B to $1.4B. No employee should be in any way surprised by what happens when you watch your company's valuation fall that much. Anyone surprised by this wasn't paying any attention to the company's operating metrics (they only made $27m last year!) to a negligent extent.
It sucks for the people let go, but they can't be surprised.
you're arguing de facto with de jure. Not a historically healthy way to argue. We aren't lawyers here.
>Anyone surprised by this wasn't paying any attention to the company's operating metrics
Dude, I just want layoffs to be signaled ahead of time. You can defend billionaires all you want and gaslight engineers for not being marketing majors. My demands are very simple.
Everyone saw 21: -50m, 22: -80m, 23: 21m, 24: 27m and knew this was a dead company walking. With one or more annual founds of layoffs since at least 2023. Oh, and low revenue growth and falling subscriber counts.
That's not marketing or gaslighting, that's expecting people to pay minimal attention to their employer's financial performance. Minimal here being on the level of possessing object permanence.
While you may be correct in the sense that, in a public acquisition statement, people should be inferring enormous context and not taking anything said at face value.
It's simultaneously true that this is the farthest thing from effective, honest, and clear communication. Reading between the lines here is required precisely because we all know that any acquisition statements made are, at best heavily coded, if not completely just fluff.
You can recognize that and still get angry that it's par for the course for such things to be not just devoid of useful information, but often actively deceiving.
Tbf, and in support of your broader point, there's no reading between the lines, because genuine intent is indistinguishable from deception with this kind of stuff, because the latter imitates the former. There's only expecting the worst, and being only occasionally wrong.
You'd be surprised, even by navigating in this comment section. I guess they continue to do it because it works. Or because they no longer care about public sentiment.
You're not wrong, but how screwed up is it that we expect leadership at companies we spend most of our waking time on to bullshit through their teeth at the people that make the damn thing work in the first place?
>I've also found reviewing LLM generated code to be much more difficult and grueling than reviewing my own or another human's code.
absolute opposite here.
LLMs , for better or worse, generally stick to paradigms if they have the codebase in front of them to read.
This is rarely the case when dealing with an amateur's code.
Amateurs write functional-ish code. TDD-ish tests. If the language they're using supports it types will be spotty or inconsistent. Variable naming schemes will change with the current trend when the author wrote that snippet ; and whatever format they want to use that day will use randomized vocabulary with lots of non-speak like 'value', or 'entry' in ambiguous roles.
LLMs write gibberish all day, BUT will generally abide by style documents fairly well. Humams... don't.
These things evolve as the codebase matures, obviously, but that's because it was polished into something good. LLMs can't reason well and their logic sometimes sucks, but if the AGENTS.md says that all variables shall be cat breeds -- damnit that's what it'll do (to a fault).
but my point : real logic and reasoning problems become easier to spot when you're not correcting stupid things all day. it's essentially always about knowing how to use the model and whatever platform it's jumping from. Don't give it the keys to create the logical foundation of the code, use it to polish brass.
I know Ubuntu, among others, used to ship Firefox without modules it defaulted into, so it would complain harmlessly and bring up an annoying pop-up-blocked style modal when the TTS module/engine was missing.
Oh so maybe they are just initialising the TTS by default, ready for those who need it for accessibility? That would make sense.
I'm on a Debian, so that ties in with what you mentioned.
It's easy to get rid of the error, I was more just curious. Thought maybe mainstream websites had started blasting speech at users as soon as they arrived.
[0]: https://www.reuters.com/legal/litigation/amazon-copied-produ...
reply