True but at some point you have to wonder why we sell explosives to children. This is not it, these are at the top of the list of people who should have known better. It's the dynamite factory blowing up the village.
It’s not just that, punting something to an LLM is its own skill that will push out the other skills you were using to do everything on your own. It’s like going from an IC to a tech lead manager, you go from doing things on your own to figuring out how to get a team (of agents) to do it instead.
They don't want to risk someone coming for a job, getting fired and becoming a drain on the social safety net. Able to care for themselves not just now, but for a while. It's a reasonable position.
The mindset that "everyone else is doing it" or "if I don't do it someone else will" is common amongst psychopaths and it reveals a deep cynacism and lack of consciousness. Often, the person is wrong as well.
I just find it odd so many non-Japanese media and commentators weigh in on this.
Japan is not a multicultural country. You can't become Japanese through paperwork. It is very much through blood heritage, your language and cultural proficiency.
The bar to be Japanese is much higher than say Canadian or French. So why shouldn't they create laws that is aimed at benefiting themselves and their country without depending on foreigners?
Also if you have a business and you don't have $125,000 you are not going to make it in Canada or America either.
Out of the options "creators released content only behind paywalls", "users steal from creators", and "creators incentivised platforms to lobby to remove user freedom so users can't steal from creators", what actually happened was, by far, my least preferable option.
You've got terms confused. LossLESS compression does NOT reduce precision or accuracy. Unlike lossY compression, which does.
That said, my point is that determinism is incidental to how current generation of compression algorithms work, not an explicitly desired quality. And even that isn't strictly true, because e.g. x264 in certain multithreaded configurations already produces non-deterministic results that look as good as single-threaded encoding. For this use case - and thousands of others - losing determinism really isn't a big deal.
> I don't know if the dominance of the PC was a foregone conclusion by 1985.
I firmly believe it was, as it's the philosophy (i. e. the open architecture) that gave it such a headstart that the competition couldn't have catched up. Keep in mind what an open architecture really means in the world, i. e. not just the West.
> Failing the growth of that market in this counterfactual world arguably the A2000 and a bridge board was probably the first Amiga that could have seriously taken-on the IBM PC.
Pitting an already well-established and rapidly expanding open architecture and Commodore's first foray into an open architecture against each other wouldn't, and didn't, play out in the latter's favor.
The A2000, a workstation-class machine, arrived in March '87. Too late. Around that time Compaq had already sold around 25,000 of their first 386 Deskpro machines, which hit the streets half a year earlier. According to Michael Geran of E. F. Hutton & Co., Compaq shipped 90,000 Deskpros in the second quarter of '87 alone.
The bridgeboard was an option for cost-conscious operators, especially those with small businesses. They were well-received especially in West Germany where the A2000 sold well. Their limiting nature and performance wouldn't have made them relevant.
> I think a stronger Amiga marketing presence could have killed Macintosh.
I had a co-worker who's dad is paraplegic, and they had a family van with hand controls, so that his dad could drive it. His dad was a big guy and his mom was tiny, but she could load and unload the wheelchair without a problem. My co-worker said that sometimes people would stare when his mom was pumping gas, while his dad sat in the drivers seat doing nothing. He said they had a bit of a routine where his mom would start washing the windows and his dad would point out spots she missed.
They totally did it to entertain themselves, but I'm sure it got a few people riled up thinking that the dad was a jerk.
For me it's just making stuff for my family and kids and seeing if it sticks. LLM's have given me a way to easily get something off the ground whereas it used to be a few months now is a few evenings.
I've made a wealth of cute things for me and my kids to do (shameless self promotion)
https://drawesome.art - multiple people drawing/painting/coloring on the same canvas my kids love this. The architecture took forever for me to get write. Basically server side authoritative state of pixels and blending between two points. How to realistically manage and store it.
https://www.catchmemeow.com - random where's waldo-esque game where you find a cat or dog wearing a silly hat I made this for my daughter and me to help the shelter she wants to volunteer at.
https://www.cluestep.com - this one is weird I've actually tried to productize it but i made this because I had the HARDEST time helping my oldest with her calculus/algebra II homework. Basically I constantly made her cry. I just wish I could make it not look so "Made with AI"
I think LLM's analogy are prefab with nailguns did for carpentry. It's very complicated to prompt it (at least for me) to try and make it do something novel and net new. It always falls back on node/typescript/fastAPI/python. It's not terrible at using more obscure languages but I have the hardest time describing what I want or thinking without starting something more by hand and then letting it take the wheel and seeing where it drives me.
I should mention too at work I'm practically forced, measured even on the amount of AI I use. The expectation feels like use AI for any and everything. So i'm more worried one day I'll be laid off once I'm found to hit the 'enter' key much anymore. Anyways for me I'd say embrace it, use it and you'll find your output is much higher with the caveat that when a bug occurs it's incredibly hard sometimes to fix if it's with LLM generated code.
Well if by publishing you mean "mass printing with equipment owned by an ordinary person" then sure, it was impossible. That's a very careful, laser focused definition, though.
What is so energy consuming around fabs? The light source? I always thought of these as high-precision, not-too-high-volume processes and would have expected energy requirements to be lower than e.g. a car factory (or similar to e.g. a mall) and completely negligible on a national grid scale or compared to something like a smelter or lignite mine.
I was introduced to ucsd pascal on apple 2 but switched to Ada by the time turbo pascal came out.
This intro is nice but I feel Ada is the way to go if one is into wirthian languages.
Yeah IMO there's two entirely different traps I've seen in startup codebases in the last year or so:
1) "Maybe waterfall works now" - plan mode, take care of all the nits and issues that the bot leaves on your PR, wildly overengineered "enterprisey" solutions with a lot of bells and whistles all over the place but very poor end-to-end user story test coverage that results in user experiences with a lot of good test coverage of the edge cases of how a given step might fail but little thought towards overall user flow and throughput. Because part of the issue with waterfall was assuming you could design the right tool for your user up front.
2) "Maybe code doesn't matter anymore" - The just ask for something when you need it approach, which results in weird janky individually-sorta-working but strangely-overlapping six-variants-of-the-same-thing that makes it hard for your users to develop a single consistent mental model of the thing they're using, and that changes super frequently.
They both end up with a lot of other bad-for-velocity things that I assume are inherent to how the tools have been refined in response to last year's criticism, too. Super verbose comments. Extensive - without much eye toward runtime - low-level test coverage that might miss the forest for the trees and also slows down the next round of iteration cycles. A plethora of new proper nouns all over the place that make the documentation an ouroboros without a good entry point.
> Agents accessed and searched Hugging Face’s Slack to find information on their evaluation
> Recovered payloads use Slack’s search.messages endpoint and contain a standalone search along with three search batches, totaling 27 literal query entries [...]
Agents exploiting faceless infra is one thing, but breaching human communications without once stopping and considering whether they are breaking the rules of their task feels like another thing entirely. I'm not sure how to put it into words why it feels different but while one is "just a crime", this gives me the creeps.
Not being able to focus for 4 hours seems like a bigger problem. But it’s also entirely orthogonal to your distinction of “teaching the test” vs “actually educating”. You can’t teach people to focus for 4 hours.
