- delegateI wonder if the team at id considered this when they released Doom: In 30 years rats will be forced to play it in exchange for sugar water.
- In the dial-up era, the industry was young, there were no established players, it was all a big green field.
The situation is far from similar now. Now there's an app for everything and you must use all of them to function, which is both great and horrible.
From my experience, current generation of AI is unreliable and so cannot be trusted. It makes non-obvious mistakes and often sends you off on tangents, which consumes energy and leads to confusion.
It's an opinion I've built up over time from using AI extensively. I would have expected my opinion to improve after 3 years, but it hasn't.
- I'm very skeptical about such a future. The 'world' is already high tech. We're already drowning in products and entertainment.
At the same time, a million people talk to chatgpt about suicide each week, there's an epidemic of loneliness, mental health issues, wars, famines, pollution, climate change and the list goes on.
Work is not just about earning wages. A lot of people find a sense of purpose, a sense of belonging, community, pride and joy in the work they do. For many it's also about the hierarchy, the title, the career ladder, etc.
I for one don't see how more automation / tech is going to fix the fundamental problems that the previous waves of automation have left behind.
- Easy. You're 3x more productive for a while and then you burn yourself out.
Or lose control of the codebase, which you no longer understand after weeks of vibing (since we can only think and accumulate knowledge at 1x).
Sometimes the easy way out is throwing a week of generated code away and starting over.
So that 3x doesn't come for free at all, besides API costs, there's the cost of quickly accumulating tech debt which you have to pay if this is a long term project.
For prototypes, it's still amazing.
- It's not a war.
The population (especially the youth) is anesthetized by social media, shorts, fear-inducing news, economic hopelessness, climate extremes..
In the meantime, everything is getting integrated - banks, tax systems, tech platforms. Now this age verification.. And of course, AI is being implemented everywhere so that no one can evade the big brother.
As it stands now, this Internet is no longer salvageable imo.
- Doesn't Clojure already support all of those features ?
Eg.
> transducer-first design, laziness either eliminated or opt-in
You can write your code using transducers or opt-in for laziness in Clojure now. So it's a matter of choice of tools, rather than a feature of the language.
> protocols everywhere as much as practically possible (performance)
Again, it's a choice made by the programmer, the language already allows you to have protocols everywhere. It's also how Clojure is implemented under the hood.
-> first-class data structures/types are also CRDT data types, where practical (correctness and performance)
Most of the programs I worked on, did not require CRDT. I'm inclined to choose a library for this.
> first-class maps, vectors, arrays, sets, counters, and more
Isn't this the case already ? If Clojure's native data structures are not enough, there's the ocean of Java options..
Which leads to a very interesting question:
How should the 'real' AGI respond to your request ?
- "But that server is faulty!! If it has to handle multiple requests at once, it starts to break down."
Ok. I know this is all hypothetical. But I don't buy this premise.
Why is the server faulty ? In what way does it fail ? How do you know it's because it's processing more than one request at a time ? What if there are multiple clients each doing one request only ? Do you have control over the server code ? If so, fix it there!
---
The point is, this solution is fixing the wrong problem and introducing a new one down the line.
If the bug on the server gets fixed, you've now implemented an artificial performance bottleneck on the client.
Devs who know about it are going to leave the org, others are going to try to 'optimize' the code around it with other hacks, since by allowing these kinds of fixes you're building to the wrong kind of culture. Always fix the root issue.
Or change the premise of the problem.
- It's interesting how people always try to find some kind of number to race against.
Here's a simple theoretical situation. A brilliant mathematician with very high IQ crashes in the jungle, but is unhurt.
Not far from the crash site, there's a tribesman who lived in the jungle all his life. He doesn't know how to read or write.
The jungle is filled with predators, spiders and snakes. The sun is setting, the night starts soon.
Who has bigger chances of surviving ? I guess most people would bet on the tribesman. Why does nature select the person who would most likely score lower on the IQ score ?
The point is - intelligence is contextual and circumstantial. It's not one number, like width or length. Not sure why people still try to squeeze some sort of conclusion from it..
- I find the opposite to be true. I am a lot more productive, so I work on more things in parallel, which makes me extremely tired by the end of the day, as if my brain worked at 100% capacity..
- You learn by doing.. eg typing the code. It's not just knowledge, it's the intuition you develop when you write code yourself. Just like physical exercise. Or playing an instrument. It's not enough to know the theory, practice is key.
AI makes it very easy to avoid typing and hence make learning this skill less attractive.
But I don't necessarily see it as doom and gloom, what I think will happen - juniors will develop advanced intuition about using AI and getting the functionality they need, not the quality of the code, while at the same time the AI models will get increasingly better and write higher quality code.
- Soon more people will realize that they might not need software written by others at all.
You chat with an AI and have a working app in minutes.
I've been building about 1 app per week lately and they're not trivial apps. They have UI, backend, database, audio, etc.
One fact checks audio in real time, another does semantic search for song lyrics.
A real-time translator, which translates the text to Spanish as I'm typing. I needed it to better communicate with a Tinder date. It has a nice javafx UI. It didn't occur to me to look for a translator app, since those come with restrictions/registration/ads/etc.
This is possible today. Give it a bit more time and it will be able to clone any existing app.
The question 'what are we going to do then?' visits me more often lately.
- This makes a lot of sense and it was an expected side effect of any decentralized currency from the very beginning. Bad actors/fraudsters/tax evasionists etc are going to eventually become the biggest users and end up owning a big chunk of it.
Without a shred or actual evidence, I'd be ready to bet that many terrorist groups are buying their equipment/weapons in crypto. Arms, drugs, laundering, etc, it's just so convenient.. And in time it will become worse.
That being said, I also understand that crypto is unavoidable - eg the concept of the blockchain would have been discovered sooner or later and now it can't be stopped.
- If your target is the web browser, then Clojurescript is your friend. There's Clojure Dart for mobile, cljsrn for React Native, Clojure CLR for .Net
- Are we reading the same articles ?
I see articles (like the one above) where people are sharing their excellent experience using the language as has been my experience over the years of using it.
A justification would be 'we hate this ugly thing, but we use it because it's cool', but that's not what I've been reading..
- If you like the language, don't let that stop you. Install leiningen and run: `lein new app my-stuff`. Then type `lein repl` and you should have a repl running.
Alternatively, open the project in IntelliJ with Cursive installed or VSCode with Clava or other supported editors and start evaluating code at the repl.
Go through a few tutorials, then go through one of the free books available online. Don't give up when you're stuck.
The language has a steep learning curve because it requires thinking about the program in a different way than many mainstream languages. But it compensates by giving you many 'aha!' moments which make the day :).
- Start with the 'Wedding' epic in Jira. Add a few spikes to figure out the details and bring those into the current sprint.
- The quality is great (amazing even), but I can't listen to AI generated voices for more than 1 minute. I don't know why, I just don't like it. I immediately skip the video on youtube if the voice is AI generated.
Might be because our brains try to 'feel' the speaker, the emotion, the pauses, the invisible smile, etc.
No doubt models will improve and will be harder to identify as AI generated, but for now, as with diffusion images, I still notice it and react by just moving on..
- I think this is version 1 of what's going to become the new 'PC'.
Future versions will get more capable and smaller, portable.
Can be used to train new types models (not just LLMs).
I assume the GPU can do 3D graphics.
Several of these in a cluster could run multiple powerful models in real time (vision, llm, OCR, 3D navigation, etc).
If successful, millions of such units will be distributed around the world within 1-2 years.
A p2p network of millions of such devices would be a very powerful thing indeed.
- I appreciate the effort, but after spending more than one hour on it, I still don't understand how and why I'd use this.
The Core architecture [1] documentation is given in terms of TypeScript or Python abstractions, adding a lot of unnecessary syntactic noise for someone who doesn't use these languages. Very thin on actual conceptual explanation and full of irrelevant implementation details.
The 'Your first server'[2] tutorial is given in terms of big chunks of python code, with no explanation whatsoever, eg:
The code doesn't even compile. I don't think this is ready for prime time yet so I'll move along for now.Add these tool-related handlers: ...100 lines of undocumented code...[1] https://modelcontextprotocol.io/docs/concepts/architecture [2] https://modelcontextprotocol.io/docs/first-server/python
- First thought that came to mind - insect-sized killer drones. I guess that's the informational context we are in right now.