i dont think its all talk, these are smart people that have been in ai since the 2000s, and they raise good points. current incentive structures are very dangerous long term
Any conversation
they too have every incentive to exaggerate because they are selling safety and/or books on the topic. I donโt believe we wonโt see it coming. Any issues that will manifest will be very visible and weโll have plenty of time to mitigate their impact.
they could be making a lot more money by just working at ai firms i fear. the thing that got me worried the hacking incidents lately, huggingface etc.
if the capabilities consistently outspeed the development of safety measures, and if the private arms race logic continues, i dont think this is a good spot to be in long term
For 30 years, productivity sky-rocketed with the advancement of automation and computing. Meanwhile, a decline in longevity was observed, correlated to sleep depravation. Productivity improvement goes to the owners class' pockets, sleep benefits the workers health.
For 30 years, productivity skyrocketed through automation, yet longevity plummeted as a direct result of sleep deprivation. While these gains accrue to the owner class, sleep remains an undervalued element of the worker's health. We are trading life expectancy for chump change.
i was under the impression life expectancy has been steadily increasing over the last century, where are these quotes from? and which date?
โฆ
That said, in Canada working class started loosing life expentancy for the 3rd year in a row, and WHO figures show a decline in improvement of life expentancy globally. But hey, I am just a no-one on the internet spewing bs :)
a decline in the improvement of life expectancy isn't the same as a decline in life expectancy, it's just that it's improving less fast now, we might be reaching biological limits however?
&หข แต แต แถ โฑ โฟ แต ~ ELDER FUTHARK:
แ แข แฆ แจ แฑ แฒ แท แน
แบ แพ แ แ แ แ แ แ
แ แ แ แ แ แ แ แ
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake
One idea that I've been thinking about is an or where it is a app so you get a new file everyday right except the app keeps track of all the files for you. the idea is that anytime you type anything it it basically makes a commit and use so anytime you type something it commits automatically after a quick pause after you stop typing.
That sounds ! Could also create summary titles with for the filenames in addition to their date so you can find what you were writing about easily. Also full text search.
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
