Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New MacBook Air

apple.com

Post reply on HN
Print view View original

61–70 of 587 posts

Re: New MacBook Air

#61

Post by saagarjha »

donw wrote: post #51
cytzol wrote: post #19

The refined scissor mechanism with 1 mm of travel delivers a responsive, comfortable, and quiet typing experience. The inverted-T arrow keys help you fly through lines of code, spreadsheets, or game environments. This isn't progress. This is the baseline. Apple have gone from bad to OK, and they're celebrating as though they've achieved something amazing.

So is this a not-broken keyboard design? I have the (now) previous-generation Air, and need a keyboard repair. Would be seriously tempted to just buy a new one if I was confident the keyboard wasn't absolute garbage. Typing on it was fine when it worked, but it double-spaces, and a couple of the other keys are now wonky. Never had a keyboard die on me before this -- Mac or otherwise.

Supposedly. I don’t think anyone has any of these yet.

Re: New MacBook Air

#63

Post by dangus »

Perhaps we can finally stop jumping down Apple's throats for daring to sell a computer this time around.

There is legitimately nothing wrong with this computer. All of its previous shortcomings have been rectified

- It has an agreeable keyboard

- It's cheaper

- It has a quad-core processor, finally

Re: New MacBook Air

#64

Post by bpicolo »

kasey_junk wrote: post #56
ehutch79 wrote: post #48

Earlier quoted context omitted.

Why would you keep rebuilding the container constantly though?

Typically build flows don’t mount the js with volumes they embed it in the image. I’m not cognizant enough of the trade offs to know why.

Optimizing your local workflows is worth the effort at every team size.

I think the attempts to make local workflows mirror production 1:1 (local k8s, for example) are misguided. They miss too hard on the productivity story. Especially once you start having to swap out local debugging for remote debugging (which only a handful of languages support effectively).

This is the biggest miss for many companies striving for microservice architecture. The local development story is terrible, and it stays terrible, without a lot of opinionated decisions around what your dev workflow needs to look like past the ~3-5 services mark. At a past gig I had to change 5 different repositories (5 separate PRs, all needing approval) to send an email. In a rails app that would have been a trivial task.

Re: New MacBook Air

#65

Post by partisan »

bjoli wrote: post #38
cytzol wrote: post #19

The refined scissor mechanism with 1 mm of travel delivers a responsive, comfortable, and quiet typing experience. The inverted-T arrow keys help you fly through lines of code, spreadsheets, or game environments. This isn't progress. This is the baseline. Apple have gone from bad to OK, and they're celebrating as though they've achieved something amazing.

Their (very) old keyboards are still amazing to type on. They went from high quality mechanical switches to bad rubber domes to okish rubber domes. The current magic keyboard is actually not bad, but I would still prefer the old alps switches.

I completely agree. My 2014 MacBook Pro purchased refurbished still has the best keyboard of all the devices I use. The Lenovo X1 I use for work is a close second.

What I noticed in the image that made me excited about this device is the function keys. If the 16in MBP had function keys, I probably would have purchased one already. I do wonder if the top spec of the new MBA is going to hold up to my usage though.

Re: New MacBook Air

#66

Post by shirshak55 »

christiansakai wrote: post #42
twsted wrote: post #11

Earlier quoted context omitted.

It's perfect from a performance point of view. I own the last generation (so no scissor keyboard) and I work the whole day in VSCode with JS/TS, Python, Go, Rust, etc.

how's your Rust compile time in this?

i don't know how is he able to compile rust. I have 2 core MBP 13inch 2017 macbook pro.

Rust compilation takes like 15 seconds for small changes in actix project. For amethyst game library i wouldn't even try.

Re: New MacBook Air

#67

Post by davedx »

rvanmil wrote: post #3

Anyone here who has experience working with JS/TS development tools (vscode, yarn, webpack, Node.js etc.) on a recent MacBook Air? I wonder if the performance is noticeably worse than a 13” MacBook Pro for this type of work.

I have a 2017 Macbook Pro and the main project I work on brings it to its knees. This is a front end project with a nodejs graphql server, TypeScript, eslint, VS.Code, webpack. I think actually the linting is the worst CPU drain, but all in all with the graphql server and front end tooling running at once, it makes my laptop slower than running the .NET core back end it connects to.

Kind of annoying. Working with a simple create-react-app project with TypeScript is fine though.

Re: New MacBook Air

#68

Post by snemvalts »

solat wrote: post #52
snemvalts wrote: post #37

Earlier quoted context omitted.

i think most people prefer to not sell their souls for advertising when it comes to their desktop environments.

Do you mean the start menu? I never open it, just use Win + number for pinned apps. Windows is not perfect but it excels in many regards nowadays and the last years, Macs were really expensive and risky. They were too expensive to just have a fall-back machine lying around (if you make serious money with you gear, every hour counts). I have 3x 2.5lb notebooks here, if one needs to be sent in, so what. Edit: just open…

Regardless of using the start menu or not, there's a lot of background tracking (for user behaviour and ads) that needs to be disabled by registry edits. In addition to those, there's probably more that cannot be disabled.

Re: New MacBook Air

#69

Post by ehutch79 »

ehutch79 wrote: post #48
kasey_junk wrote: post #33

Earlier quoted context omitted.

It seems pretty typical for js backend systems to be heavily containerized such that I’d say it’s approaching the default deployment mechanism.

Why would you keep rebuilding the container constantly though?

kasey: For deployment that makes sense, but for development, that seems like a lot of work to be happening.

If you change a small bit of css, the whole container is rebuilt? That seems super inefficient to me?

My backends arn't JS, but I still couldn't imagine rebuilding a container everytime I changed a piece of code. Right now I change a file, django picks up the change and reloads. No noticeable delay.

Re: New MacBook Air

#70

Post by saagarjha »

ryanlol wrote: post #58
baybal2 wrote: post #7

I like it how they have to almost shout "no butterfly switch keyboard there" now Thank you Louis Rossmann!

What does the weird conspiracy theorist dude have to do with this decision by Apple?

He has his faults, but calling him a “conspiracy theorist” is uncharitable.
Post reply on HN