Curioso 🍉 🇺🇦
boosted
1990s web experience
- Open site in browser
- Watch framework of site gradually appear
- Start reading site text
- View images once they load
- Click a hyperlink to more information on the thing you're looking for
2020s web experience
- Open site in browser
- Wait for Cloudflare to verify you aren't a bot
- Wait for background movie to load
- Dismiss cookie popup
- Decline to subscribe to their mailing list
- Decline to speak to a chatbot that promises it's a human
- Scroll infinitely looking for the information you want that's probably not there since it's all generated text intended for other robots to read anyway
And that's why reality surpasses fiction.
Half of the work is getting to know what clients really need, and half of development is really prototyping in order to check those needs. If clients would know precisely what they need, 75% of us would be unemployed.
20 years before, if you would tell anybody that we were going to end carrying in our pockets mics, cameras and a variety of sensors managed by lots of software made by random people that could be used to spy on us, they would think you were asylum material. But here we are.
First, there were no asynchronous operations, but we needed them for calling servers (and later other things). So callbacks were invented to have them.
But callbacks got us into callback hell, so promises were invented to abstract them. There were 3 different incompatible kinds, but it seems nowadays we are finally settling on the one and only.
But promises still were not really intuitive, so async/await were invented to hide them under syntactic sugar.
But async/await It is a incomplete abstraction, because you have to create promises anyway. And yes, newbies find it easier, until they are forced to create a promise and they don't know what it is. Besides, being forced to mark an old function as async only because you just added a line with the word 'await' is not so great, really.
So the countdown for the next abstraction begins...
May the documentation chaos ensured by never finding an example using your favorite abstraction not bury us all.
Con el tema de ChatGPT la cosa está empeorando rápidamente, porque ese tipo de artículos los genera como churros. Y no son pocos los que se han dado cuenta de que colgando un montón de artículos generados con eso puedes subir mucho en Google. Si a eso le sumas que hay mucha gente diciendo que para qué quieres un buscador, si le puedes preguntar a ChatGPT y ya está, pintan bastos.
I agree, dashed is great, and a real saver when your design has reds and other really intense colors.
Bien está que se intente mejorar; pero cambiar algo que es crítico que funcione bien y que sólo usas una vez cada tantos años por algo inestable y lento...
Pero si había que romper algo, mejor ahora que no en la próxima LTS. La mayoría de la gente no va a instalar desde cero esta versión, a fin de cuentas.
Y aún tienen tiempo para corregir cosas.
<dialog> tag is supported in all major browsers.
But I agree, most of ARIA roles should have semantic tags to replace them. The less ARIA attributes you have to use, the better.
I like much more 'outline: 1px solid red', because it doesn't have any effect on sizes, and we barely use outlines anyway.
But totally agree with console.log. And console.warn. And console.table. And all console goodies.
Or a scifi film about a time traveler trying to kill them all, with the customary time authority trying to preserve history. He just escaped from a dystopic psychiatric ward, hence all the psychoanalysis hate.
No idea. Very likely the issue is with the theme.
And yes, we web developers are too used to test on Chrome & friends and forget about Firefox (shame on us!). Or Safari (who wants to support something that requires a damn Mac to test on?).
To each its own. I got used to the new editor; it is good for embedding or doing complex things; and if you only write is only one more click, most of the time. Jetpack is big, not cheap, but solves many things; depends on your needs.
Well, then you are already down the rabbit hole. You are doing already 99% of the stuff (posting+updating+making backups). The other 1% may be solved by hosting support or Google+community. If you are lucky, that 1% may not even exist (I'm talking about rare cases of botched updates, daemons not running...).
(Disclaimer: I'm not a writer).
In fact, any of the seven deadly sins should be more than enough. Even laziness: imagine a mischievous and manipulative co-worker, spreading lies in order to avoid doing his own work. And being successful.
There are many other motivators. Most of all-powerful villains in fantasy and scifi act out of boredom or curiosity, for example.
If it comes preinstalled, you have a complete blog with comments, etc. by default, ready to use, and a ton of themes. Anything else, you will need extensions. There are a lot, but if something doesn't fit, though luck.
Other CMSs (like Drupal) are much more versatile, so you don't need extensions most of the time. But they are much more complex to configure and administer.
If it is for OSNews, I reckon it will suit you perfectly.
The most idiot proof way to host it is in Wordpress.com, because in the cheapest tiers they don't let you shoot your own foot installing themes or extensions, and they manage all the updates and security fixes; in fact, creating and managing a blog in the free tier feels a bit like creating and managing a Gmail account. You can use it to wet your feet or try it; and then migrate to a dedicated hosting if you need/want it.
That would explain why nobody talks about assembly language anymore.
Manda narices preferir que tus hijos aprendan sobre sexualidad y género a través de internet antes que de sus profesores y de los libros. Sabiendo la flora y la fauna que se van a encontrar. Y que los niños lo primero que se pasan entre ellos es lo que más les llama la atención.
@toastedlord@masto.ai
Bueno, esto explica lo de antes de que te has vuelto conservador. Con semejantes perspectivas de futuro...
Curioso 🍉 🇺🇦
boosted
Things that do not and will not exist:
- a perpetual motion machine.
- a computer solving the halting problem.
- an AI with a trillion parameters, trained on users' data, that preserves privacy and is robust to misinformation and data manipulation.
Have a good start of the week.
