I think it is refreshing. They don't half-ass things into the framework. They take the time to do it right. They let every feature fight for its life, and put their effort into LTS and minimizing number of issues and API changes related to the features they do deliver. As a developer I really appreciate this. I don't have to totally rewrite my entire application every new version because the implementation wasn't properly thought through.
I used to have this opinion about ASP.NET then ASP.NET Core and the great churn happened. It's finally settled down again, but boy the in-between years were chaotic.
Not just the Framework -> Core migration itself, but the power to make breaking changes went to their heads, and they started quickly tearing up everything only to change their minds again, such as a short-lived "project.json" syntax.
Django is exactly the technology I'd pick if I wasn't already super familiar with the .NET stack. It's got the "batteries included" feel without the chaotic confusion of a million ways to do things. It doesn't have the breaking changes churn that happens elsewhere too.
I don't know about ban, but parents today are so totally disconnected from the dangers associated with scrolling. Kids today live in their phones. The ones that stay away are going to have such a competitive advantage. So maybe not forbid, albeit that would really serve the community, but the goverment should get off their asses and start informing schools and parents about what their kids are doing to themselves.
But it is a super-difficult problem to solve, because a lot of parents depend on just letting their kids sit with their phones a couple of hours every day to enable wfh etc (or in worse cases, go out with friends to socialize).
My wife is super-aware and is a stay-at-home mom and even she thinks it is a real challenge (mostly because of what friends are allowed to do). We have rules that say no screens (with exceptions for research, school work, some programming) during weekdays. We banned TikTok and Roblox years ago. The kids get 1 hour per day during weekends. These rules, when my wife introduced them, made a HUGE difference. They're different kids (they get so bored they clean their rooms, play chess, read books, play with Lego, don't have problems with their chores etc).
Same. We've been working on a huge React project for several years. Lots of graphs, 3d models etc ... and it is super-snappy. Only slow part is a WebGL-based chart component that visualizes 2-3 M rows of signal data. We can probably decimate the signal data to improve performance, but that has got nothing to do with us using React.
N.B. No one is using the app from their mobiles. iPad and computers only.
Our reasons for choosing React when there are so many alternatives: prior knowledge, ergonomics, easy onboarding, ecosystem.
Super-snappy for who? You? with a $4000 Mac Book Pro? Even with 6x CPU slowdown in Chrome, that's not enough throttling for these modern computers to test with.
I make this argument all the time and people think I'm an idiot, which is fine. But JSX to me is reason that Svelte and Vue aren't as good. They are faster IMO but with JSX it's nice that you can make a form and then each part of the form can be broken out into separate methods.
The reasoning I get all the time is "Why would you want to do that? That's stupid".
It's just so much nicer honestly. I'm not a react fan at all but that's one thing I miss about it.
Huh? All of the modern web frameworks let you delegate a component to a team and use it. What does react do here thats special?
Honestly, if anything I find react's modularity story much weaker than the competition. In react there's no page-wide state and the story around styling components with CSS is a huge mess.
In comparison, Svelte components feel much more modular & self contained because the styles are embedded with the component in a standard way.
A developer on a team I worked with many years ago accidentally committed our AWS keys in a repo. Got a $30k bill due to a an enormous amount of EC2-instances being spawned. We contacted AWS and they were very understanding and reduced the bill to $50.
Dracula is a very well-crafted theme, but I can't help feeling like it makes my editor feel like a toy. I've gone a lot of different themes, but the only (dark) one that has worked out for me is everforest [1], with the following modifications:
vim.cmd [[hi Normal guibg=#111111]]
vim.cmd [[hi EndOfBuffer guibg=#111111]]
vim.cmd [[hi StatusLine guifg=#ccdc90]]
vim.cmd [[hi link TSLiteral TSString]]
vim.cmd [[hi TSField guifg=#c4b89b]]
vim.cmd [[hi TSTag gui=italic]]
vim.cmd [[hi TSTagDelimiter guifg=#859289]]
vim.cmd [[hi TSInclude guifg=#d699b6]]
vim.cmd [[hi link TSInclude Purple]]
vim.cmd [[hi link mkdWikiLink TSURI]]
vim.cmd [[hi link mkdWikiLinkStart Blue]]
vim.cmd [[hi link mkdWikiLinkEnd Blue]]
Notable themes I've kinda liked (but had some problems with for various reasons): moonfly and zenburn
Many of the systems I build do require routing/filtering/messaging and I have yet to find a more pleasant environment to work in than Erlang. I can agree that the ecosystem is a bit lacking if you want to build a quick web application, but out of curiosity, what are you referring to when you say that Erlang lacks a lot compared to modern languages?
How do you feel about Phoenix (and, by extension, Elixir) as something that might scratch the 'quick web application' itch?
As a web developer, I've been quite happy learning Elixir/Phoenix in the past year, and learning Erlang has been on my list, so I'm very interested in hearing from people with more Erlang experience when it comes to 'web stuff'.
I must admit that I have not (yet) played with Elixir. It looks very exciting though!
I don't do much "web stuff" with Erlang. The closest I go is probably HTTP-based control interfaces for other services (routing, validate input, do something in the system and return a response).
I usually turn to Python and Django when I want to create web stuff. Generic views, the forms API, DRF, admin, and an ORM that integrates well with all of the aforementioned are godsent if you just want to get something online quickly.
I still have old Django project that I wrote for a customer back in 2007. Besides upgrading Django two times a year and updating the ui a little it has been running w/o problems ever since. And I still find my way around the code instantly.
I have yet to try something that comes close to being as convenient to work with.
I love Phoenix but creating form on that framework feels needlessly complex.
Formex library is outdated and doesn't seem to work on Phoenix 1.4 but it makes it so much better to create form.
With Phoenix form library you have to add code in several files (schema, context, controller, view, and template). I can never remember all of it correctly so I have to refer to pragprog text book all the time. Formex require less.
I don't believe this is some sort of a deal breaker but it is important enough. There are tons of web app require forms CRUD operations admin like stuff to insert data via web.
Having someone close suffering from being burnt out: please be careful. It will hit you like a hammer from nowhere and can cause irreparable damage if you do not take it seriously.
Lets hope people donate a little today to relieve Phoronix of some of the preassure.
