• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • Profitable for who? The one hosting it foots the bill. If it was federated, all drivers could host their own instance like WordPress and a single app would connect to all instances and all drivers.

    Agencies could start up to manage the tech for a negotiable fee if the drivers in the area didn’t want to bother with the tech.

    Whether or not it could be profitable entirely depends on the hosting and delivery model. One guy could host the tech stack and charge maintenance fees and be in the green.

    If you mean rich, then yeah, nobody would probably be rich. But you can build a small business as a hosting provider no problem, and the drivers would probably get a better deal. Uber employs so many people it requires they charge money. There’s a tipping point when the service provider becomes so large that their sheer operating expenses start to necessitate increased costs. Breaking up provides better value in that case.




  • Great games feel fewer and farther between after this long. Yes, you get a Witcher 3, or Baldur’s Gate, or Zelda sometimes. But really, and it sounds fucked up to frame it this way, they’re merely excellent. And I’ve played a lot of excellent games, so unless one is on a tier never before experienced by anyone on Earth, eventually things feel less special for some reason. It’s fair to say that some games are innovative, but they are very few. The best we usually get is stuff we’ve seen before, just insanely well polished/tweaked on ocassion. Ultimately, there’s not a lot new if that makes sense. It’s sort of a been there done that vibe, and it’s probably just a sign you’ve played too much good shit. Like an addict that has hit the same pipe too many times lol.







  • To be fair, there’s huge demand for a Swift-like language in the space Go operates, since nobody will ever adopt Swift outside of Apple use cases. Rust is excellent, but garbage collection is not awful at all for most Go use cases. I think Go designers made a mistake by not introducing sum types sooner since there are many ergonomic issues that could be solved with them.

    This may lead people to argue for JVM-based languages, but Go seems like a leaner and nicer package overall and compiling to static binaries so simply is still a major winning feature. That and I think Go still has performance advantages over JVM and C#.

    In many ways I think Swift is better than Go as a language, but we effectively will never have that as an option people freely choose to use so it would be nice for Go to close some ground where it can and where it makes sense to do so. Go is what people already want to use as a starting point, so it makes sense for it to try and modernize a tad.




  • The truth is that JS is currently “good enough” and all the best (adopted) web frameworks are either server or JS based.

    I believe the chunking of script files is currently a bit more natural as well.

    WebAssembly is the best choice for certain kinds of apps but most web apps are good enough with JS. If communities pour a lot of polish into WASM frameworks you may start to see wider adoption. Diversity is good, but it does need to be asked why WASM + DOM is objectively better than JS + DOM. It complicates the ecosystem a bit because you might fracture it for no good reason. Should there be Rust, Python, and JS DOM rendering frameworks? Is there a benefit?

    If you have a more traditionally native app you want to port, that’s different. That’s a great fit for WASM. Personally I see it becoming more popular when it’s a good replacement for desktop technology and the DOM isn’t used at all (go straight to GPU). I’m a huge fan of WASM, but I also write a lot of web apps and don’t see a super convincing reason to adopt WASM to effectively make the exact same thing. As-is, it’s great for augmenting an app though.

    Wait for garbage collection and sockets and you might see the paradigm start to shift.