I find it's way easier to build crappy React apps than an HTML-first approach.
An "old school" Ruby on Rails/Symfony/Django app, with templates, usual get/post forms etc, frames you and pushes you in using the standards and relying on browser default behaviors.
In JS-heavy apps, it's as easy to code normal `button` elements as it is to code clickable `div` elements. But with the divs you just forget to handle keyboard nav, proper element roles, etc. It's easy to create fake links, not relying on `a` tags, using an internal JS router that doesn't expose URLs, doesn't handle middle click mouse, for no particular reasons.
In less JS-heavy contexts, the easiest way to do is to use proper HTML so you are less inclined to mess up.
Even on codebases that use a decent framework like Next.js that handles those for you on paper, it's often we see people not very aware of the benefits of using proper semantics and standard behaviors, and you easily end up with web apps with poor UX in the end.
I'm astonished by how far those aim trainer tools go haha, and how popular they are. I discovered Aimlabs[1] recently, which seems like the most popular one, and it has 6 000 people playing right now.
Yeah, I'm really not sold either on the speed aspect.
I'm using warpd which is a similar tool, and for me it's really not about speed, but more about the comfort of keeping my hands on the keyboard. Still using the mouse a lot but warpd is often handy.
I agree the discomfort, or after a while, even the pain when using the trackpoint, is something very noticeable on modern thinkpads. I don't recall being this annoyed with the older thinkpads like T61, x200 and all. Or maybe we are just getting old and more fragile haha
To nuance this, the more you go up in specs, the more macbook become more expensive than comparable framework. Try to compare with a 64GB framework or 2TB framework for example.
One benefit of framework is you may not need to get storage, and just go use the one in your current laptop, saving around £200. And you might even try to source the RAM on your own to save a few more. But I admit that is somewhat difficult these days haha.
We should also consider that repairability, upgradability and open hardware/software support don't come for free and are features that are worth paying for.
I'd bet a bunch of money that it's barely used anymore.
Only benefit of trackpoint nowadays is that you don't move your hand. Otherwise, it's all downsides compared to modern trackpads, especially haptic ones like here. It's less precise, less ergonomic. Nowadays I'd rather move my hand a few centimeters off, than put regular strain on my forearm and struggle being precise with the pointer.
And most thinkpad users, employees of big companies, don't care at all about the trackpoint. I'm pretty sure it's only kept for the thinkpad brand and to keep the vocal minority of us geeks pleased.
yeah, why don't vendors just copy the damn thinkpad layout? It's a _pro_ line-up, we deserve a keyboard where _pros_ can directly use the keyboard shortcuts in their _pro_ apps :)
I wonder if the 13 pro uses qmk or similar for its keyboard firmware, I think the framework 16 does, so maybe? Being able to re-arrange on the hardware level the Fn-key related layer would make it the perfect laptop keyboard for me.
Otherwise, it rubs me the wrong way to pay 3 000€ for a premium device with a rather frustrating keyboard layout. But oh well, paying even more for macbook pros that have an even worse keyboard makes the pill easier to swallow I guess.
I have to agree the keyboard layout is a noticeable bummer. The only actually impactful one I can find on this laptop on my side for now. So, props to the team still!
Man, this looks really, really impressive. It basically solves every issue we could find to the framework 13. Can't wait for the reviews.
Accepting the prices of the ram shortage era is still painful, but even with the 64gb option, here in France it's still a great deal compared to similarly configured premium thinkpads or macbook pros.
I used big blue button and jitsi a lot in the past and this is a really good contender. Using Meet basically every day at work and it's really great. And the project gets new useful features regularly.
(I'm obviously a tiny bit biased since a made a few commits to the project a while ago, but pinky promise, you should try it!)
I agree that Laravel models rub the wrong way, but that shouldn't instantly remove Laravel from the equation when thinking about what tools to use for building a website.
Laravel is great for shipping things fast. Sometimes, that's what you want, even if that means a less maintainable app in the long run. Because sometimes there is no long run; you know it will just be an app made by you only as a rather one shot thing.
Same goes for wordpress. Lots of devs like to shit on it by default. But its like people shitting on PHP because of the PHP 5 days. You'd be surprised how quickly you can build really complex content websites with Wordpress. Way quicker than with barebones laravel or symfony. And with not that ugly code ;)
vscode is noticeably slow compared to sublime text or zed, even without any extension. You instantly notice it when switching files or typing things that trigger auto-completions.
In the end the feeling is drastically different. It weirdly makes for a more peaceful experience to have such a snappy editor.
vscode wins thanks to all its extensions, where basically every language is supported and most features you can think of are there. But it's kinda like modern react. You know better alternatives exist, like solid or svelte, but the community is so big, it stays the easier choice in the end.
Yeah, nowadays the trackpoint is just a bad pointing device. As laptops get slimmer, trackpoints get less precise and less usable. And they hurt our wrists.
We just have to let go. A haptic trackpad is miles better now.
Used this in the past and it's my favorite tool to make presentations now. It's really the most dev friendly tool I managed to try, and I guess I tried a few.
The most interesting thing for me is that you can write your own Vue components for your most specific use cases. Makes it easy to write some rather interactive slides. And it saves you from having to learn some presentation-specific software, some motion design or video making tool. Just quickly code your way through everything.
An "old school" Ruby on Rails/Symfony/Django app, with templates, usual get/post forms etc, frames you and pushes you in using the standards and relying on browser default behaviors.
In JS-heavy apps, it's as easy to code normal `button` elements as it is to code clickable `div` elements. But with the divs you just forget to handle keyboard nav, proper element roles, etc. It's easy to create fake links, not relying on `a` tags, using an internal JS router that doesn't expose URLs, doesn't handle middle click mouse, for no particular reasons.
In less JS-heavy contexts, the easiest way to do is to use proper HTML so you are less inclined to mess up.
Even on codebases that use a decent framework like Next.js that handles those for you on paper, it's often we see people not very aware of the benefits of using proper semantics and standard behaviors, and you easily end up with web apps with poor UX in the end.