Hacker Newsnew | past | comments | ask | show | jobs | submit | fishgoesblub's commentslogin

Looks generic, and has the stereotypical abysmal keyboard and trackpad as any laptop made in the past 10+ years. Put this in a room with a few other laptops and it'd be hard to pick it out from the crowd. The only thing it has going for it are the raw specs, but it's eventually marred by the price for what is a poor typing and trackpad experience.

> Looks generic, and has the stereotypical abysmal keyboard and trackpad as any laptop made in the past 10+ years.

I wasn't aware that generic laptops had moved to haptic touchpads and up-firing speakers over ten years ago...


It is the common buttonless style that is annoying to use compared to something with actual mouse buttons like an older Thinkpad.

That is not haptic feedback touchpads.

> A haptic feedback trackpad is a stationary, non-moving touchpad that uses motors (like Apple's Taptic Engine) to simulate the physical sensation of a click.


They claim it has a haptic trackpad, so I don't think that's what most manufacturers use.

The hardware is designed in house and is the only trackpad that approaches macbook levels

Yeah starlabs uses a lot of glass trackpads in their products and are known for good builds; certainly this will be better than a thinkpad or something. The common complaints for their laptops are usually battery life (I know the horizon battery life was famously abysmal, roughly 3 hours of use), although I'm not sure how long this battery will last.

This is genuinely pathetic. I wish I could do my job this poorly and still be employed.


It's A Trap! ~ Admiral Ackbar

Keep in mind that it's easy to call someone else incompetent whenever their thing doesn't work, but we have no full idea what's going on behind the scenes. They could be very competent people in an unwinnable situation (like being forced to use Azure).

I have a feeling this will go the way of Optane and once it becomes useful they'll pull it and shelve it while keeping the patents/license of course so no one else can improve on it

cries I am sad at all of the cool designs that would work with optane if it had been widely adopted. We desperately need more points on the latency/cost per GB curve.

One can only imagine how much money Intel would have made from Optane during the ongoing RAM shortages. It would be absolutely perfect for warm KV cache, and potentially good for MoE expert offloading.

Of the 3 software AV1 encoders, the only one that is fully dead is the Rust encoder (rav1e). If people truly wanted memory safe encoders/decoders, they would fund and develop them.

https://github.com/memorysafety/rav1d got funded and developed. it is unfortunately a bit slower (typically by a single-digit percentage) than dav1d.

I can totally understand why people would want a memory-safe decoder, but a memory-safe encoder is niche. Finding a memory-safety bug in a decoder is a matter of finding a single unchecked integer field somewhere; finding a memory-safety bug in an encoder requires first finding some sort of logic bug in the encoder and then crafting an adversarial input that survives a number of highly lossy transformations.

Compare the number of CVEs against x264 (included decoders don't count!) and FFmpeg's H.264 decoder.


Fully dead in what sense? Seems like it still has active development to me.

It hasn't had any proper quality/speed improvements in years. Only thing that has changed is updating deps and some bug fixes.

Encoding is a way, way less risky thing to be doing compared to decoding.

There are many paths to memory safety, even if the one Rust project seems to be going nowhere.

There's other memory-safe languages, and there's formal verification.

e.g. seL4 favors pancake.


> If people truly wanted memory safe encoders/decoders

Really? How many codecs have your neighbors contributed money for the development of, just curious.


I think these conversations are directed by the parties funding the efforts. Example: "we (large company) want a fast AV2 decoder" -> they pay a specialized team to do it -> this team works in C for the most part, so it is done in C. If there were financial incentives to do it in Rust, they'd pay more for a Rust decoder.

I'm more interested in the idea of general "people" (the commons) funding complex video encoders. I do wish that was the world we lived in, however :)

Given Netflix's involvement with SV1-AV1, (not even that) indirectly, at least 1.

1.0 and still has the wrong colours when ran in Wayland and lacks bitmap font support.

> 1.0 doesn't mean "done". It also doesn't mean "perfect"

Create issue in the Zed Github repository?


Don't need to create an issue, both have had issues for them for 2 years.

https://github.com/zed-industries/zed/issues/9057 https://github.com/zed-industries/zed/issues/12629


Sort of a recurring theme, I find. They have 600+ issues that have been open for over a year, was hoping they'd drive down the backlog a bit before declaring victory

Go look at any large project, they have 500+/1000+ issues and many are ancient. Chrome, Firefox, you name it. I wouldn't be surprised if many issues have even been solved or need new reproduction steps but there's a difficulty to triaging all the issues as well.

> I wouldn't be surprised if many issues have even been solved or need new reproduction steps

All the ones I'm subscribed to are straight-up feature gaps versus competing IDEs. Though of course, there is significant selection bias to my subscriptions


Yeah I can see that. I probably wouldn't be subscribing to issues that weren't feature requests/gaps very often. Ones that are tied to bugs are the only others that come to mind that I'd subscribe to but just thinking about my own dev experience in various jobs and how even there our internal backlogs of issues would have unclosed, out of date stuff, I think some portion of issues in public projects would be too.

The colour issue also affects MacOS - every time I open VSCode it strikes me just how more vibrant the exact same colours are, rendering there.

It's easier, and somehow more reliable to self-host a Gitea instance on consumer hardware than it is to rely on GitHub.


I rest my (6 year) case. [0]

[0] https://news.ycombinator.com/item?id=22868406


It's surprising, and disappointing that this hasn't happened sooner. A real shame that it took a browser company other than Mozilla to make (In Rust no less!) adblock-rust. I wonder if this could've been a native Firefox feature and selling point years ago if Eich wasn't kicked out.


I'm so glad Brave arose from all this overblown mess. What a solid product, one you disable the web3 crap. Using Firefox and derivatives feels like using a Java application on the desktop years ago. Every interaction seems foreign. Meh.


At this point it'll be better to have alerts for when GitHub is online, rather than offline.


I remember when Zed's main thing was "collaborative" editing. Not as profitable as AI I suppose.


A or C you'll have to use a dongle regardless.


Haven’t used USB-A on my Laptop in years. Don’t even have an adapter.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: