midrus

26 ms·

1. 211.▲
   by midrus 5y ago

   ignores long term survival of life due to lack of better alternatives
2. 212.▲
   by midrus 5y ago

   > SPA or hybrid rendering is just plain better, It is not for your end users, just for the developers building it because it has a better dev experience. As a proof of this try most sites out there which are built as an SPA vs the ones
3. 213.▲
   by midrus 5y ago

   Github, Hey, and so many others are examples of Rails applications with complex interactions. Server templates and partials rendering doesn't mean "I reload the page on every click and can't write any javascript because I onl
4. 214.▲
   by midrus 5y ago

   Wait until you see JavaScript written by Java programmers. It had "Java" in the name.... right??? right!!??
5. 215.▲
   by midrus 5y ago

   This is crazy. Plus all components are now singletons. Plus you won't be able to use almost any 3rd party hook. Plus probably breaks devtools, linters, and more. What about just using Vue or Svelte if you don't like the way React
6. 216.▲
   by midrus 5y ago

   Looking just at the "syntax" to discard or like something is very naive in my opinion. Thinks such as the performance, the reactivity model, the "gotchas", the ecosystem, the libraries, the tooling, etc are far, far, far
7. 217.▲
   by midrus 5y ago

   It is not an "HN thing". These machines are damn fast in day to day use. Absolutely zero heat, zero usage of fans and incredible battery life too. I see a lot of hype and fanboys around here regarding certain techs, but these mach
8. 218.▲
   by midrus 5y ago

   I suppose it depends on what you subscribe to. > I'm driving or walking or cooking or cleaning. > It's noise that minimally engages What's a better alternative? Listen to the vacuum cleaner? to the other's cars en
9. 219.▲
   by midrus 5y ago

   Yeah, scrum masters. Just when I thought it couldn't get any worse.
10. 220.▲
    Have Single-Page Apps Ruined the Web? (“Transitional Apps”)(css-tricks.com)

    2 points by midrus 5y ago|0 comments
11. 221.▲
    by midrus 5y ago

    You seem to have misunderstood everything. Engineers where the ones pushing for it, that's why they ended up building surrounding services in python3. Transitioning big, heavily used, daily changed by thousands of engineers codebases i
12. 222.▲
    by midrus 5y ago

    I'm talking about many years ago (6 more or less). And this company has a HUGE codebase. It has its managements problems too, but the situation I'm talking about didn't make it any easier.
13. 223.▲
    by midrus 5y ago

    I stopped using python long ago, out of the frustration with the breakage caused in the ecosystem first due to the 2/3 transition, and then by splitting again the ecosystem with all the async stuff they introduced, when having instead
14. 224.▲
    by midrus 5y ago

    Wohaa!! I had one of those. Those were my first few years with computers and I was just learning with a friend of mine how to build and tune them to support better Doom, Quake and all the games we were playing at the time. I think this stuf
15. 225.▲
    by midrus 5y ago

    Give a try to Unpoly[1]. I really, really, really love it and feel like this is what 90% of projects need, and maybe the remaining 10% are the ones that need a full frontend framework. Unpoly augments HTML in a declarative way, it comes wit
16. 226.▲
    by midrus 5y ago

    But why do we need a new rails? That's what I don't get. Just because we want to use JavaScript?
17. 227.▲
    by midrus 5y ago

    I don't think 100s of engineers working on a massive next.js application would be any easier. At scale everything is complex.
18. 228.▲
    by midrus 5y ago

    Best release ever
19. 229.▲
    by midrus 5y ago

    I'm going to be downvoted to hell for this... but the more I see the level of complexity and amount of engineering going into this, the more I miss Rails and how simple things are there, given most of us are just building CRUD apps any
20. 230.▲
    by midrus 5y ago

    Google App Engine?
21. 231.▲
    by midrus 5y ago

    Bad news for you: as apps grow bigger, they become complex and difficult to maintain in every single platform or language.
22. 232.▲
    by midrus 5y ago

    Worked for a company that made extensive use of elixir. It was a disaster, not due to the technical stuff, but because of every other aspect of a technology choice: - Near impossible to hire experienced people - We had to write from scratch
23. 233.▲
    by midrus 5y ago

    Given how bad it works, I bet it runs a kubernetes cluster with all 100s of microservices inside my browser.
24. 234.▲
    by midrus 5y ago

    Or even better, provide a top level configuration option, like: ReactDOM.render(element, document.getElementById('root'), {memo: true}); Just dreaming...
25. 235.▲
    by midrus 5y ago

    This is great. And great explanation of the reasonings. I wonder why React doesn't provide a configuration/flag/option to just do this by default if anybody wants to.
26. 236.▲
    by midrus 5y ago

    I like Unpoly[1] a lot. Seems like the perfect companion for django template based projects. It's like htmx but with more features. https://unpoly.com/
27. 237.▲
    by midrus 5y ago

    > Then all that extra complexity starts sucking more when you figure out that an old server-rendering framework would work just fine for the app you are developing, it didn’t have to be a SPA in the first place. But React was chosen just
28. 238.▲
    by midrus 5y ago

    I'm an extremely happy Brave user since last year, and my default search service is duckduckgo. Not missing neither chrome nor google search.
29. 239.▲
    by midrus 5y ago

    To me right now it is the uncertainty of all the things that maybe could go wrong with nuclear power vs the certainty of a global collapse.
30. 240.▲
    by midrus 5y ago

    Well, it's not ideal but what is the alternative? To me it is either nuclear or watch how the next generations are going to be the last ones, because there is no other solution (or improvement at least) at sight right now.