Depends on who has their ears in terms creating policies around technology.
816 karma · joined February 17, 2023
Depends on who has their ears in terms creating policies around technology.
At least DeepSeek freely gives back the benefits.
All three either have security or stability issues, which seems to get worse, not better, as microsoft goes more into AI. Where is the AI productivity (10x by some accounts!) within the company going to?
Only once was there a noticeable breakage when a command like `git log` in the terminal would spit out all its output instead of displaying one screenful at a time. I'd expect someone following stable releases wouldn't experience any breakages.
> Matz has said as much. He’s described Ruby’s design as starting from a simple Lisp, stripping out macros and s-expressions, then adding an object system, blocks, and Smalltalk-style methods. The features most Rubyists fall in love with aren’t the object-oriented ones. They’re the functional ones, dressed in friendlier clothes.
With hindsight, does that hold? If not, then how would we know a model is truly dangerous to release?
Would it be 80s technology everywhere but widely deployed? Or would things have advanced further - better compilers, more ergonomic languages, better platforms etc? I don't know. But I suspect we'd still have needed people studying computer science to advance the state of the art.
Now looking forward 30-40 years from now, will everything still run on 2020s technologies?
Too much VC money and big tech influence in the JS ecosystem made the web worse in some ways.
Maybe we'll get there, maybe not. These days I only hear of datacenter investments.
And they became just good enough that more people didn't go into Lisp/Smalltalk instead.
Their creation C and UNIX won over the more advanced LISP and Smalltalk systems because they were simpler to implement. Even their own more advanced Plan 9 based OSs could not displace the more widespread unix-like systems.
It seems distribution and 'good enough' to rely on always wins. IMO, dynamic languages like Perl, Python, Ruby, JavaScript, PHP and the heavily marketed Java provided good enough high level facilities that have prevented people from reaching for Lisp and Smalltalk.
Looking at it through this lens, perhaps C++ was the vehicle for strapping some high level facilities on a widely adopted low level performant language that made it just good enough of a technology for wide adoption.
While minimizing energy spent worked well in historic periods where survival was hard, in this era of abundance and a complex, interconnected and fragile civilization, the same instinct becomes harmful.
Just because AI can do something that resembles work should not mean outsourcing work to it. Mathematicians should not outsource their work to AI just like programmers should not outsource programming to AI.
Humans working with AIs in a tight loop means intellectual work becomes more high-level and creative, but a human should always own the work, validate it and stake their reputation to it. Simply ban any humans who produce low quality work using AI.
Generally, it is conspicuous how American companies are absent when it comes to state of the art open models. Meta tried for some time but it seems they've given up.
Are we already questioning the value of a human brain because of Large Language Models? Glorified search over a vector space? This is actual psychosis
If these claims were true, why don't they point the agents at the numerous stability and security issues they have across their various platforms?
I'd prefer it if people looking at hiring numbers would compare it with the pre-pandemic levels.
There are people who write important software that the world runs on, but they do it outside the 'industry'.
A real industry should be responsive to events of nature, or at least the market, not vibes.
Could you expound more on this? Are you suggesting that less energy use in data centers would help the world's poor?
If the programmer gets to intimately understand the user's experience software would be easier to use. That's why I support the idea of engineers taking support calls on rotation to understand the user.
Both can be true at the same time, a product manager who retains the big picture of the business and product, and engineers who understand tiny but important details of how the product is being used.
If there were indeed perfect product managers, there would no need for product support.