Can't wait for my son to try this. He has general coordination issues due to a brainstem injury but the eyes are probably the part of the body he can better control.
I'm not a fan of Apple's software and didn't have a great experience with the Vision Pro but I am excited to try it out.
Consider it like era's/decades. It doesn't have to be perfectly accurate but it gives you a rough idea of a point in time. When I think 'web 2' I think of Digg, Facebook, social media. At the time it was more of a buzzword but in retrospect it defines that era. It doesn't have anything to do with 'versioning' the web.
Rails was released 16 years ago (according to wikipedia). Rocket just got the first release that builds on stable rust. Thus: Give it 15 years, we'll be there!
In case of Django, I actually don’t feel much difference in this regard—it’s always been very much batteries included. It is natural for a project to have no dependencies but Django (and maybe psycopg2 bindings), business domain-specific dependencies excluded. Happily used it since before the first major release.
Indeed. Apparently the support for stable Rust was merged onto master months ago, but there hasn't been a release since then. 0.5 should be the first version that builds on stable Rust according to this thread: https://github.com/SergioBenitez/Rocket/issues/19
I want to caveat this by first saying I’m a fan of Rust in general, but does one not see the irony in the article’s claim to the effect “yes, it’s ready as a Rails replacement”, yet requires you to use an unreleased dev version of a library to even build from a stable release of the language?
Yeah, and I don't know how anyone could claim its a Rails replacement. Diesel, warp, rocket et al are great but the DX and feature completeness aren't there yet.
That said, with Cargo using the unreleased version is as simple as changing `rocket = "0.4.5"` to `rocket = { git = "https://github.com/SergioBenitez/Rocket" }` so it's not like you even have to clone it manually. You can even specify branches if you urgently need a PR and patch entire workspaces with forked versions and so on.
I kinda disagree, I think people are more pessimistic about fracturing than is warranted. For greenfield work, it seems like people have mostly converged on React and Vue, which are conceptually fairly similar. State libs have changed, but again the concepts translate pretty well. Similarly, webpack is the lingua franca. Years ago, we had a new build tool every week, and multiple competing frameworks (backbone, angular, and ember) with very different approaches.
I don't think any One True Way will emerge. Svelte is coming out to challenge React and Vue, Alpine+Laravel LiveWire/Phoenix LiveView challenges the concept of needing a front end framework, WASM is challenging needing Javascript at all, and Snowpack/Parcel/Rollup are coming for Webpack's crown.