Nowhere near enough to produce their content. Ad revenue from YouTube is less than 15% of their budget. Patreon, institutional sponsors, their online shop, more.
And it will not be limited to LLMs. In just a few years, they will likely figure out robotics and continual learning. Then all jobs are affected. I'm very worried about what's coming for all people who rely on wages to survive.
All jobs will be affected before robotics. When there are less white collar jobs there will be more people competing for blue collar jobs.
More workers competing means lower pay. Less good paying jobs means less customers. Less customers means less jobs. This is an over simplification, but is one possible future.
On a message board institutionally subservient to Capital there is all the talk about how LLMs will take wage jobs away, but little analysis of why people rely on wage jobs to begin with.
But never mind that. Get money or die. Every rat for herself.
It even seems the "more correct" uppercase form of ß is now ẞ, not SS.
> Traditionally, ⟨ß⟩ did not have a capital form, and was capitalized as ⟨SS⟩. Some type designers introduced capitalized variants. In 2017, the Council for German Orthography officially adopted a capital form ⟨ẞ⟩ as an acceptable variant, ending a long debate.[4] Since 2024 the capital has been preferred over ⟨SS⟩.[5]
They did not. Participants from Liechtenstein and Switzerland don't even care about that letter (Swiss orthography does not make use of it), so they are not even a good place to begin such debate.
> It even seems the "more correct" uppercase form of ß is now ẞ, not SS.
But that is wrong. In german I only know of ß aka downcased version.
ẞ seems another character. I have no idea what it is, other than looking
close to ẞ, but it most assuredly is not existing in the german language.
There is simply no uppercased variant. 'ss' is "Doppel-s' - that is not
ß. In german we have "das" (which is the), but it can be "das" or "dass"
depending on the sentence, in particular after a ',' character. I often
misspell it, since I prefer "das", when in reality sometimes one has to
use "dass". But 'ß' is very different to that - to claim that 'ß' is
equivalent to 'ss' is simply incorrect. I have no idea who that
"Council for German Orthography" is, but clearly they don't know anything
about German. Who put that Council in charge of anything? Are these drunks?
The claim that the capital has been preferred, is also factually wrong. Who
is writing all that?
That is not a unified authority for anything. It
is totally unclear to me why the wikipedia article
claims that this is legally binding for anyone.
That's just factually incorrect. Is Wikipedia no
longer proofreading?
Who are you to decide what does and doesn't exist in the German language? You are no more authoritative than the Leibniz-Institut either.
Edit: The Leibniz-Institut is just the publisher. The author, the Rat für deutsche Rechtschreibung, is legitimized by the German (and six other countries') government.
Yes I know, but it is highly regarded and many high reputation organizations choose to use it as a reference. What more can you ask for in this space? There are no final arbitrators of a language. Nothing has a meaning as a source.
Wikipedia says ẞ is "preferred", which is plausible when an organization with an impressive name declares it preferable. Nobody says it's legally binding.
> I often misspell it, since I prefer "das", when in reality sometimes one has to use "dass".
It's confusing because both can mean "that".
"That is true." = "Das ist wahr."
"He said that it is true." = "Er sagte, dass es wahr ist."
Many mathematicians are now saying that (human!) understanding is (and was) the true goal of pure math. Not proving theorems itself. But I don't think that's correct. Otherwise the mathematicians would be happy about the new math genius AIs (which are infinitely patient in explaining anything), rather than feeling the threat of AIs beating human mathematicians in proving various conjectures.
I rather think pure resesarch math was merely partially about understanding. The other part was a sort of game, where you win prestige if you are the first to prove a famous conjecture, and where you feel like a "researcher", a math scientist of sorts, who "discovers" the secrets of the platonic math universe.
Pure mathematicians are a bit like gamers "exploring" the procedurally generated worlds of Minecraft (or rather, solving procedurally generated puzzles in a puzzle game), while feeling like they thereby make serious scientific discoveries.
The difference is that no actual gamer would delude himself into thinking he is a researcher.
> Otherwise the mathematicians would be happy about the new math genius AIs (which are infinitely patient in explaining anything), rather than feeling the threat of AIs beating human mathematicians in proving various conjectures.
I am unhappy about the “math genius” AIs because they’re part of the ongoing trend of commercializing basic human interaction.
On the other hand, often a "quick and dirty" solution unexpectedly becomes the foundation of a lot of other stuff, which can be a persistent pain in the future, while the cost of rewriting the whole thing increases the more other stuff depends on it.
There are two poles: On the one side is making everything an unmaintainable pile of quick hacks, on the other side is over engineering everything. You want to be somewhere in the middle.
Totally agree, it needs a careful balance. But is it possible to know when to use what?
Anecdote: A couple years ago I migrated a 1M+ LOC application from one database to another, cutting the cloud hosting costs practically in half. This was absolutely massive for the company. It took a bit less than a year, but was possible because the people who designed the application didn't write any hardcoded queries, and everything went through an ORM or a query builder. Everything was built to an interface, even though they all only had one implementation. This turned out to be absolutely critical when we had to add the second implementation (and because we needed to maintain compatibility for the original implementation at the same time due to some one-off contracts) and the migration would not have been worth it cost-wise if the proper architecture wasn't in place from the start.
Now take the same application. It has tons of complicated architecture stuff implemented in house. Parts of it are definitely overengineered. It's been apparent when doing other upgrades and finding out "oh... this doesn't work because it's using a custom JSON serializer" that the choice to do that was poor.
In the end, I think the right choice for that application was the complex design that allowed those big migrations. For others, they might never do that and only get hit with downsides.
What it needs is likely a good vision and someone smart to know what to abstract and what to not abstract such that it will have been a good choice 15 years down the road.
In my 25-year career I’ve experienced easily fifty times as much pain from underthought and hastily-implemented systems than I have from overengineered ones.
Sure, build user-facing stuff cheaply and ready to be thrown away as requirements change. But libraries, tooling, and infrastructure that everything else is built on top of should have thought and care invested in it. This will return dividends.
We spend so much time as an industry worried that somebody might put five percent more effort into a project than it’s worth, that the overwhelming majority of engineers have no idea whatsoever of how to build something to be reliable, to be easily iterated on, and to last. And so we spend tens of times more effort trying to build on top of a mountain of crap.
> On the other hand, often a "quick and dirty" solution unexpectedly becomes the foundation of a lot of other stuff
This is how Access "databases" and Excel spreadsheets often become mission-critical in SMBs. "We'll deal with needing a database server down the road..."
I'm not sure I agree. I think you can write a simple-but-not-hacky implementation that does only what is necessary, and is also easy to maintain and extend later.
Of course, you never really achieve that ideal, but you can keep getting closer to it as you gain more experience.
"Easy to extend" arguably means including more abstraction and making things more general than they need to be merely for solving the current problem. There is a trade-off here.
"Easy to extend" for me means keeping things decoupled (as opposed to adding extension mechanisms etc.).
Of course there's a tradeoff (there always is), I think my point was just that this option doesn't really seem like it fits between "quick and dirty" and "over engineered", though I suppose that probably depends on how you picture that continuum ;)
> The Family Game [a Famicom clone] was manufactured by the Argentine company Electrolab S.A.[41][42] They distributed Super Family Electrolab Ending-Man (based on Ending-Man Terminator clone) and Electrolab Family Game with official distribution of Supervision.[43] At the peak of its popularity, its sales amounted 95% of the argentinian console market.[44]
They make money from ads.
reply