Better to use date of birth as that doesn't change at all.
6,970 karma · joined March 29, 2008
https://github.com/cabalamat/catwiki_p3
Better to use date of birth as that doesn't change at all.
There should be.
And an entirely manual brake.
I agree, and this is often overlooked. Knowing what doesn't work (and why) is a massive help in searching for what does work.
I don't know if that's still the case. I do think that it would be worth creating systems that mix the ANN and GOFAI approaches to AI.
According to https://www.moneysavingexpert.com/tax-calculator/ , someone in the UK who earns £100k takes home £67,049:
>Earn £100,000 in 2023/24 and you'll take home £67,049. This means £5,587 in your pocket a month. Over the year you'll pay £27,432 income tax and £5,519 in national insurance.
I say "on the whole" because there are always counterexamples to any maxim. The article realises this and mentions 2: DRY and SoC.
Writing good software is often a matter of taste.
Yes they could, so the question is why didn't they?
I suspect the answer is that there are lots of factions within the EU, some want to ban it and some don't and what they've done is a compromise.
So why don't pathogens evolve to display PD-L1 on their surfaces, to make immune cells harmless against them? Or do they?
Which suggests to me that while kagi might be good now, if it gets popular it may undergo enshittification in an effort to monetise its popularity.
Another advantage of Haskell is that its side-effect-free nature makes it harder for a rogue AI to put in malicious code, thus helping to solve the alignment problem.
It may be that languages and OSes will be specifically designed to put everything in a sandbox (or multiple layers of sandboxing), which will also be helpful when humans write code.
> while less-used languages tend to produce worse results
I figured that might be the case.
> Haskell may or may not need a manually-tuned LLM to generate solid results.
One possibility would be to write some Haskell programs, that illustrate paradigms in the language and train the LLM on them. Then get the LLM to solve similar problems, and automatically test how good its solutions are on grounds of solving the problem (passing test cases), performance (time and space used) and how easy it is for humans to understand the programs.
Then use those solution to train the LLM to be better at Haskell, and give it another set of slightly harder problems to solve.
In this way it would learn programming pretty much as humans do, by solving incrementally harder problems.
In the long term I can imagine that the output languages of code generators like this might be ones specially designed to work well with AI code generators.
- It has a wider selection of content. I don't have to faff around looking for which content is available on which service.
- There is no DRM.
- Do these services even work on Linux? I know BitTorrent does.
Does whatever maximizes Amazon's short-term profits, probably.
Yes. XML was basically superceded by JSON, which was far less verbose and clunky.
I suspect Java applets fell out of fashion because they could only manipulate a rectangular area of the screen and not the DOM. Did the DOM even exist in 1995?
The problem is -- from the content companies' point of view -- that if there is one streaming service and multiple content creators then the steaming service will make the lion's share of the money.
So the big content companies all want to have their own streaming service.
This of course drives people back to the pirates.
What I want to know when learning a new software system are what are the main classes/concepts in it and how they relate to each other.
I recently started getting into Javascript 2D game programming.
MDN has a nice simple straightforward tutorial[1] on how to make a Breakout game in pure Javascript. Having read this tutorial, it all fits my brain. It's simple and I understand it.
There are also lots of frameworks you can use, e.g. Excalibur, which also has a breakout game tutorial[2]. This does not fit my brain: there are vast number of classes to learn, and how everything fits together is not obvious at all.
While I was reading the MDN tutorial I was thinking to myself how I could easily build a framework to automate a lot of the stuff. (No doubt many others thought the same!) If I did build such a framework I would understand it well. It would fit my brain. But would anyone else understand it? Possibly not.
I suspect that what makes a framework easy to learn is, above everything else, good documentation.
[1]: https://developer.mozilla.org/en-US/docs/Games/Tutorials/2D_...
Looks like someone's been doing too much enterprise Java progamming!