Interesting to see how many things Gary got wrong.
432 karma · joined March 27, 2013
[ my public key: https://keybase.io/arxpoetica; my proof: https://keybase.io/arxpoetica/sigs/8d0pru2QVDe8OGHMBqxMLOBDGuuOMF3Kpc7WU5safXY ]
nuff said
...until we have speech muffler envelopes built into our devices.
That day is sooner than we think.
AI will likely steamroll current copyright considerations. If we live in a world where anything can be generated at whim, copyright considerations will seem less and less relevant or even possible.
Wishful thinking, but maybe we'll all turn away from obsession with ownership, and instead turn to feeding the poor, clothing the naked, visiting the sick and afflicted.
[1] https://www.cbsnews.com/news/the-roman-empire-tiktok-trend-w...
This Internet Canvas seems like a step in that direction.
Lots of software growth, but much of that is hardware related.
> A farm boy, his inspiration for scanning an image as a series of lines came from the back-and-forth motion used to plow a field.[1]
- https://insights.stackoverflow.com/survey/2021#section-most-loved-dreaded-and-wanted-web-frameworks
- https://2021.stateofjs.com/en-US/libraries/front-end-frameworks/
- https://twitter.com/Rich_Harris/status/1589675637195042817I voted for `@nest all` because I don't think it's a feature I will EVER use, so I wanted it to be dumb obvious that someone is using it by explicitly putting @nest in the code. That way if I encounter it in the wild, I'll be less likely to confuse it with SCSS nesting, for example.
This is the gist of the whole comment. The person posting is not complaining about a bad Svelte experience, they're complaining about bad programming practices.
That's because there is no syntax for reactivity in JavaScript, period.
Svelte Kit is just the equivalent of (an opinionated) Next.js, Gatsyby, or Nuxt.js framework. Those frameworks are also incredibly opinionated on purpose.