201–210 of 251 posts
>But this is the same company that seamlessly transitioned its entire stack from PowerPC, to x86, to x64, and eventually ARM, with most users remaining blissfully unaware this ever took place. Also from 6502 to 65C03 to 65C816 to 68k to PowerPC... But Apple ][ users were painfully aware of the 68k transition. ;)
When reading through the comments here, I really feel like the article was misunderstood. My summary of the article is: Point 1: React solved all the right things, but its current trajectory, does not prioritize developing the fundamental tooling we need. React does not allow us to build a new Figma (consistent undo/redo in collaborative settings, immediate low-latency mutation of app state to reflect user changes an…
> React does not allow us to build a new Figma (consistent undo/redo in collaborative settings, immediate low-latency mutation of app state to reflect user changes and building fundamentals to SaaS interoperability) If I wanted to write the next Figma, the first thing I’d reach for is Phoenix Liveview + Channels with Vaxine/AntidoteDB or some other eventually consistent CRDT store for collaborative editing and host i…
Not to dismiss your argument/stack preference, but forgoing the front end for a graphic design tool might prove difficult. EDIT: But yes, CRDT-backed stores are definitely the way to go for a requirement like this.
React now is as mature as PHP4. Wake me up when it gets to PHP7 at least.
I've been doing front end since the late 90s and I disagree with many points here. One thing I do agree is the rant at the end about zoomers. We see stuff like tailwind popping up which really reflects the zoomer ethos of not wanting to learn fundamental stuff like CSS. "It's so easy to get started! Why would I learn anything else?" I think gen Xers and late boomers will be the most tech developped generations becaus…
I argue that it solves a clear design deficit in CSS. You cannot have tight coupling with CSS and a lot of the time you want tight coupling. In-line styles are insufficient, so we have tailwind. It’s an API to css that lets you tightly couple your styles. The re-usability of those styles is accomplished by composition of components or composition of atoms via @apply.
Earlier quoted context omitted.
No, it won't. Web is an ever changing platform, with a lot of churn. The most long lived framework currently is emberjs. But it is not the hottest, so you won't find it discussed much. The most "future proof" framework is "React" which is the one mentioned in Original article. It goes without saying but React is the cause of a lot of churn in js ecosystem, particularly due to its "no-battery included" approach. ## wh…
> that angular 2 should have been renamed. Didn't it? I recall it was called AngularJS when it was v1. (Yes, I'm purposefully nitpicky here, you're still right a completely new name could have been helpful here)
After angular 2, Angular team decided to rechristen 1 as "angularjs". But they didn't (cause couldn't) change stackoverflow and other sites content
>But this is the same company that seamlessly transitioned its entire stack from PowerPC, to x86, to x64, and eventually ARM, with most users remaining blissfully unaware this ever took place. Also from 6502 to 65C03 to 65C816 to 68k to PowerPC... But Apple ][ users were painfully aware of the 68k transition. ;)
And calling the ARM transition seamless is also quite amusing.
Earlier quoted context omitted.
> I recently learned that GitHub has a discussions page which is separate from the issues pages. The people who are good won't be using that. When I was a student working on my thesis I realised I was too advanced to ask questions on stackoverflow and I would not be receiving useful help there. My issues were too uncommon and specific, because the simple ones that stackoverflow is good at solving were not blocking me…
The fun of programming begins at the point that stackoverflow/Google begins to cease providing ready-made answers.
The only things worth posting to them are information you yourself weren't able to find on the internet.
Can any Web Dev framework survive long enough to be stable? If I learn some fancy framework today, I expect to use it for years to come else my knowledge and time is wasted.
No, it won't. Web is an ever changing platform, with a lot of churn. The most long lived framework currently is emberjs. But it is not the hottest, so you won't find it discussed much. The most "future proof" framework is "React" which is the one mentioned in Original article. It goes without saying but React is the cause of a lot of churn in js ecosystem, particularly due to its "no-battery included" approach. ## wh…