That is the value of other companies doing that and you going to poach those new seniors. With the money you saved not training those juniors you can offer better salaries and still have higher profits.
Yeah, I have looked through those. I remember personally as the Ontario one was going through. Even then it already had a huge backlash, and people were opposing to it because of "fairness and etc.". Unfortunately none of those tests can help with understanding what would happen to inflation, jobs that nobody wants to do, life satisfaction of middle class, and everything else, to be honest. And I also understand that trying it out on any large populace is incredibly expensive.
It’s of course not the same as UBI, but something close to it - basically everyone is entitled to it and while it’s really not a lot you can survive off it.
My personal page runs on 11ty since the last 3 years and I enjoyed it a lot.
I’ll probably replace it with pure HTML soon - I found that I don’t need a SSG anymore, I can just use a local LLM to generate HTML out of markdown files and I never use any fancy features anyway.
> ChatGPT responds with a fully-populated HTML template. All I have to do is copy and paste it into a new file in my project, run my custom script, and then push the changes.
This actually sounds more troublesome to me than adding a markdown file into a Git repo somewhere, and having Hugo/Astro/whatever automagically regenerate all the HTML files from markdown.
But that's probably because static site hosting services have come very far from the S3 bucket days.
The "build step" with Hugo/Astro might be slightly simpler. But as mentioned in the post, I find it surprisingly nice not to have to write strict Markdown. It turns out (at least for me) that formatting with Markdown still feels akin to creating a finished product. It's nice to just be able to type something out without thinking too much and have the LLM "get what you mean".
Local LLM feels like the wrong tool for a file converter? LLMs shine in natural language processing, but their statistical nature doesn't fit consistent file conversions as more Turing-like programs.
But the text file has some markup syntax beyond human language? Point being LLMs are subpar for acting on formal grammars, like cracking a nut with a sledgehammer. That's why its important tools like 11ty and pandoc remain.
That’s somewhat true (in my case it’s it’s laughably simple though).
I also never said that tools like pandoc are obsolete now. Just in my case they are already overpowered and I might migrate to something simpler soon.
Otoh i might just run the current version of 11ty indefinitely and never upgrade.
I'm also using 11ty on a couple projects, but I abhore the npm ecosystem.
I'm considering letting an LLM generate a flat python script to replace what 11ty does for me. Once removed from the fracas, it should be stable for decades.
Yea I tried Astro but I don’t want to learn their way of doing things, have breaking changes every x months/years and who knows in a couple years they maybe also are screwed.
Pure HTML will work probably forever. Previously it was too much manual work for me to write it but now the LLM just spits it out, easy as
> Someone in power doesn’t get to choose - the board of directors do. Who’s job is to act in the best interest of shareholders.
Alas, shareholder value is a great ideal, but it tends to be honoured in practice rather less strictly.
As you can also see when sudden competition leads to rounds of efficiency improvements, cost cutting and product enhancements: even without competition, a penny saved is a penny earned for shareholders. But only when fierce competition threatens to put managers' jobs at risk, do they really kick into overdrive.
Since the majority shareholder(s) can decide to replace the board of directors, it’s not the board of directors who holds the (ultimate) power, it’s the majority shareholder(s).
The problem is that they need to find some way to not only make the money back but multiply it.
That’s where the “you’re getting screwed” comes into play - we don’t know yet how they will screw us, but it’s gonna happen
>Git was built because the commercial license of BitKeeper became unworkable for the Linux kernel community.
BitKeeper was free to linux kernel developers with a "but no reverse engineering" clause, but Tridgell went exploring of his own volition because he wanted to and kinda sorta violated that, so the license was cancelled by BitKeeper.
I'm not taking sides or upset about any part of this, I just wouldn't call that "becoming unworkable for the linux kernel community"; that would be like "the fence around your yard became unworkable for me in my desire to trespass on your property so I climbed over it"
what Tridgell discovered was pretty dumb and could be considered a distinct lack of a fence, but he connected to a socket and typed "help" and it dutifully printed out a bunch of undocumented useful commands.
Yep, something that is sadly becoming more and more common. People with solutions spending insane money trying to convince others that a problem exists.
Skill issue. It's the most popular VCS in the world by a huge margin, millions of devs use it every day just fine, countless forges have been built around it, and there's only one semi-compelling alternative frontend (jj). If you honestly find Git challenging, how are you coping with software engineering? Git is the easy part.
Millions of dev use it in the most rudimentary way, occasionally lose their stash, rm their local repo and start over, ask the office expert for help every time they need to figure out where-the-foxtrot that commit came from, don't even attempt to use reflog or bisect or interactive staging, etc.
I don't see it either, funny how people had a knee jerk reaction without even visiting the thread and validating that the phrase even exists. Maybe it's even further down but without logging in I can't see it.
