I think you can set it on internal repos, but then you need to allow-list internal code. People act like this is simple + solved, but it's not. It turns into 100K-1M's of LLM tokens on a semi-regular basis, or "just hire a build infra team for your side project" pretty quickly.
"Bigger screen" (i.e. being bigger on the length/width dimension) is a bad thing in this discussion. Some people want a programming/writing laptop that fits in a handbag, so that they don't have to decide to bring it, but can just leave it in their bag the way many people do with an iPad.
Amen. I have a GPD Pocket 4 as my go to because it, a second screen, a 40% keyboard, and the arc mouse all fit in my surprisingly small bag along with chargers, cords, and a bunch of non laptop related stuff (e reader, pens/notebooks, some small tools, a miyoo, etc).
It is, however, an expensive fucking device. $2300 maxed out these days (which I think is $800ish more than i paid. Hurray ram...) or $1400 min specs (which are still quite nice).
I'm glad to see other options at that size (Pocket 4 is 8.8", but my second screen is 10") but a literal quarter of the cost. 80% of what I do on the pocket could be done something like this Minibook, and I don't give a shit if the keyboard/mouse sucks because I've got my own anyways so long as I can tent it.
There will be those days where I might need to do some local heavy lifting and regret not having the Pocket, but I'm also happy to know if it dies on me tomorrow I've got options that aren't shell out another $1k for a tool mostly used for coding.
I really liked the 12" MacBook (although my all time favourite computer was the 12" PowerBook G4 - chunky by today's standards but I just loved it).
I saw a review of the MacBook Neo where the reviewer was yearning after the 12" - but suggested that Apple has made UI elements so big with such ridiculous spacing and border radius that it would be almost unusable at anything less than 13".
Which would not surprise me in the least - I struggle with my 16" MBP and this crappy UI "framework".
> it would be almost unusable at anything less than 13"
Native resolution on a 13" MacBook Air is already pretty unusable. Out of the box, the 13" MacBook Air (physical screen resolution 2560x1664) is configured with display scaling so that the “looks like” resolution is 1470x956 (i.e., macOS renders everything at 2x1470x956 – 2940x1912 – and then scales it down to match the display for output). If you dial the “looks like” resolution down to 1280x832 (so that the rendering resolution matches the output resolution; because, say, you prefer that every UI element not be a little bit blurry from being scaled down), you'll find yourself unbelievably short (ha) on vertical resolution. You basically have to turn dock hiding on. Even then, fixed-position headers are very common on websites these days, so between that and browser chrome, you'll often find that actual webpage content is crammed into the bottom half of the display.
gotta have dock hiding & menu bar hiding & compact toolbar/tab settings for browser. only 80-90px of wasted height. The rest is web view. I can't think of any website I frequent having that fixed-position header either, so I'm gucci.
My partner (who isn't in tech, and isn't generally interested in tech) would probably literally stand in line for an updated version of the 12" MacBook on day one.
The _feel_ is very different though, even if the dimensions aren’t numerically. It was around half a cm at its thinnest, it was 250g lighter, and 23mm less deep.
I think at those sizes, what reads as small differences give an outsized experiential factor.
Timing. The core 2 generation was right before we hit a plateau in processors. An i5/i7 macbook from 2014-2015 felt pretty good for 5-6 years, until the m1 came out, and you can coast for another 2-4 years being annoyed some people have a faster machine before they start baking features into the OS that make your machine feel even slower. That’s 7-9 years of use depending on your tolerance for being behind the curve. Mine’s high, so I got 10 years out of it.
Conversely if you bought an i7 macbook in 2019 it would have felt out of date in just 2-4 years, when everyone has an m1 or better and things are starting to slow down from OS changes that expect apple silicon.
If you bought an m1 just a year later in 2020, i’d guess you’re feeling fine 6 years on.
Part of that I think was that it was the first SSD laptop many people had had, so the fast boot up times were mind blowing. I had two, a work and a personal one, and I miss them terribly.
Confirmed. Minibooks are amazing in cramped locations (for example, airplane seats), or just to always keep in the bag for support.
There's nothing in the market like them, which is a shame - I think a slightly better quality Minibook (Chuwis are plain crap) would be a very solid laptop.
I just responded above, but you might want to look at the GPD Pocket 4.
It is NOT cheap ($1300 min spec) but it's also quite a bit more powerful and with better ports (full size HDMI and Ethernet). It's not for everyone, but it blows my mind how little competition it has given how useful its been for me over the years.
8.8" is a bit too small for my use case, but... oh my, their Win Max 2 is a very impressive machine (10.1") - I'm really shocked at the size. I'm confused by the price, though - 6500$??
Legion Go (1st Gen with the removable controllers) would be better. Without the controllers, it's basically a 8.8 inch PC tablet. Would be a great portable machine. With an added bonus of the controllers converting to a desktop mouse.
I so wanted to love the Steam Deck, but it's a device with a 7 inch screen that occupies a massive volume on your bag. Unless you know you're going to play a fair ammount, it's not worth carrying around.
It's a fantastic console, but a mediocre general purpose computer.
A Steam Deck is a bit more lumpy than the Minibook. I find it a lot easier to put my Minibook into a rucksack as it's thin, so it can just slide between stuff. The Steam Deck is quite a lot bigger, though I often take both on holiday as they fill different needs.
This laptop is plenty powerful enough. The N150[0] is similar single threaded to some 8th gen i7s which many still use to code (including myself). Should run many claude sessions at once, too. I am not sure I'd want to compile large Rust projects on it, but Node/C++/Java works fine.
Depends what code you are programming. Unless you are doing significant number crunching, 3D work, or local GenAI, there is an awful lot that spec can do. If you are working on a multi-user system and it is slow processing your actions as a single tester on this, then you have a heck of a lot of optimising ahead unless you want your production users to hate you!
Maybe you'd save running a large test suite until back at base with the branch checked out on something beefier, but for on-the-go coding I expect this spec would do just fine for many. The reviewer's comments about the keyboard would be my concern, not the limits if what it can run.
I was running gentoo on a 2011 Macbook Air for years with no problems. These computers are more than fast enough to compile and run code. They aren't going to by my first choice for reencoding video or running a build server, but for local development you really don't need a lot unless you're working on the type of stuff that really actually requires special or very powerful hardware.
Or get what fits your preferred routine if available, instead of changing to match others?
Though my experience with this brand is mixed at best so I'd personally give this one a miss, especially given the reviewer's comments on the keyboard.
Agreed here, with prices for used x1s its a no brainer. Although I get the appeal of super small and lightweight devices and even had eee pc way back, but started having insane headaches after working with small screens, so guess its just not for me.
My x1 carbon gave me nothing but trouble from the beginning. I couldn't even move it too fast lest I risked it locking up. Additionally, my wrist strain got considerably better after ditching it for a comparably priced M2 that blows it out of the water in every conceivable category.
Sounds like you got a lemon. I also have an X1 carbon, and it's been a great upgrade for me. My biggest complaint is the eraser isn't as easy to use as my old toshiba. The eraser is important to me -- my hand gets numb using a trackpad.
I remember my first full time frontend job I applied to in like 2013 the job listing said I should know ember, backbone, and angular. I was kind of living out of my car so I just studied up a bunch on Ember at the time at random Starbucks.
It turns out they didn't use any of those and didn't ask questions about them in the interview. :) After a year or so they did start using Angular though.
Anyway, I did end up playing with ember and backbone around that time. Cool to see it's still developed.
It's not that bad, but when compared to C or Go, it's not something that I would like to type by hand. At least Java has IDEs which reduce the amount of verbosity you need to type. I know you get safety, but the verbosity and cargo is is a con in my opinion.
What they don't need is hardcoding support for five JS package managers in their python files.
In the post the maintainer says that an older version of bun "results in the ejs lockfile being ignored".
The reason is that they never committed the necessary lockfile despite listing "support" for that bun version.
They have separate lockfiles for other package manager versions: bun.lock, deno.lock, package-lock.json, pnpm-lock.yaml.
This part of the comment is also interesting: "which is a significant security concern for users when considering all of the recent npm supply chain attacks".
If you would set up a proper build for the JS artifact instead of committing four lockfiles to your repository, users would not be as exposed to npm supply chain attacks.
They used to have their own "youtube script interpreter" that was kind of fascinating.
But yeah as you said they switched to proper js runtimes recently.
reply