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

Windows has gotten more stable, that's for sure, but I have seen BSOD's on every single edition of Windows, and that's only on my personal life. In my time in corporate IT I can tell you that Windows is generally much more problematic than MacOS for a variety of reasons, though modern MacOS certainly has its share of issues. But again, that's in a corporate IT environment, not regular consumer usage. Not sure how you got away with no crashing in your Windows experience, but congratulations!


I didn’t mean to say it never happened. It’s just that when it happened it was a memory stick, MB, or other non Windows specific issue


Luck of the draw is very different from having the capital to invest in bots and buying up units to resell at higher prices. You could say they're lucky to have that capital, but economic privilege isn't necessarily luck either. Scalpers do not add value to the market no matter how you slice and dice it, they aren't a consumer of the product they're merely capitalizing on demand to create greater scarcity than there otherwise would have been so that they can demand higher prices. A pretty clear value detraction.


Considering that this is a brand new release of a frontier model that Anthropic is hyping hard, I'm not sure that the conclusion to draw from their repeated attempts to use it is that it's impressive... Anthropic is promising that it's impressive and we're all trying to test it out.

I, for one, have tried using it several times today and the guardrails kept switching the model back to Opus, so I have no clue if it's impressive or not.


The point he's making is that a QR-based flow that doesn't require downloading and installing an app, and instead uses the already-installed web browser, is even lower friction and can be used by ordinary folks just as well, if not better, thanks to having fewer friction points. Requiring an installed proprietary app to manage a physical device that would otherwise be manageable via a web interface is not a net improvement to the usability or accessibility of the product. Especially if it's something you set and forget, "normies" are not going to go back to that app for a very long time and likely will forget about it. Hard requiring app setup for a router is a play to sell usage and location data, it is not looking out for those that aren't "computer people".


I've had more QR codes direct me to my device's app store than I have to a web site lately.


On one hand: A thing that requires an app for setup does not necessarily require a login to some new party's outside service; it often gets shaped that way, but it does not need to be that way.

On the other hand: A thing that requires a web browser for setup does not necessarily allow strictly-local configuration; it often gets shaped that way, but it does not have to be that way.

There's no rule or law that says that these things have to be one way or another. It's a moot distinction.

> Hard requiring app setup for a router is a play to sell usage and location data,

Speaking of moot points: It's a router. And by "router," I mean: It's a whole-ass black-box computer with some Ethernet ports, a collection of radios, and an Internet connection. If/when companies decide to be in the business of selling usage and location data, they don't need an app to do that. They can just package it up and send it forth. (Location? From wifi? Yeah, that's been a solved problem for a long time now. It was first demonstrated to me in 2008 with the OG iPod Touch, which lacked both GPS and Bluetooth, but did an amazingly-good job of delivering the beholder's location using a combination of observed wifi signals and a central database.)

---

Moving on:

I guess we can talk about things like web browsers, IP addresses, QR codes, and SSIDs, and setting up routers using our pocket supercomputers.

Old way: Fire up router, manually connect to its SSID (it used to be wide-open; these days, there's usually a password printed on a label instead), set it up with a browser, and then at the right points manually connect to the newly-configured SSID instead, and [optionally] manually go to the new address (if chosen) to continue configuration (if necessary). Manually remove the old factory SSID for cleanliness. (I cut my teeth on this method and I like it just fine, but I'm one of those computer people.)

QR+browser way: Fire up router. Connect to its SSID with a QR code. Connect to its web interface by scanning another QR code. Configure the thing. Connect to the new SSID manually (or perhaps invent a workflow to scan and use a QR code using only 1 pocket supercomputer). Optionally continue configuration by remembering the name/IP of the device, or maybe printing a QR code or something. Manually remove the old factory SSID for cleanliness. (Login to third-party server at some stage? Yeah, maybe. See above.)

App way: Fire up router. Download app using familiar processes (perhaps including a QR code). App temporarily connects to router's default SSID. User uses app to configure router. At the right times, the app automatically disconnects from the old SSID, adds the new SSID to the network list, and reconnects using the new address (if selected). Optionally, continue configuring the device using the app. (Login to third party server at some point? Yeah, maybe. Again, see above.)


A real router has no radio. It has no SSID. It routes traffic. It applies a set of ACLs to determine if traffic should be forwarded. That’s it. No switching. No WiFi. Just routing. If routes traffic on the wire.


Yes. In the purest technical sense, a router routes.

A Cisco 2501 is a router.

But words can mean more than one thing. Both in the common vernacular and in the context of these Motorola-branded devices: A router is a thing that routes, and also includes radios, and SSIDs, and switching.


They're two completely different codebases... even if they are 100% feature parity, it's 100% different code. They should absolutely be separate from each other, with different issues lists. Clean separation of two different codebases isn't a strange concept...


Its not 100% different code though. Docs, build instructions, C++, Typescript...

The issues should absolutely be kept. The rewrite was file by file translation so logic bugs would remain. It's valuable to ensure the memory bugs are in fact fixed. Starting the issues from nothing does not make any sense to me.


Judging by the comments, Bun as a company doesn’t give a single shit about community. The only reason it is in the same repo is tracking down issues, discussions, etc. Those would be hard to migrate.


Ever hear of SLi (now called NVLink)? It's a GPU interconnect that's been available for a good long while now on high-end Nvidia GPU's. I believe AMD's implementation is called Crossfire.

GPU interconnect speeds are a big bottleneck today for GPU's in AI applications. Data can't move between them fast enough.



I search a lot. Heavy heavy searching. Kagi's no-BS approach to search gets me to relevant results much faster than any other search engine. And the ability to down-rank or block unreliable sources only sharpens that experience.

I have used, and continue to try on occasion to keep my opinions updated, all the big search engines. DDG, Bing, and Google. The search experience is really not there for me in those 3. Bing consistently produces poor results, DDG is a bit better but I still have to manually sift through poor quality results to get what I want, and Google makes me scroll past a lot of bloat and ads first to get to quality results, with more ads interspersed throughout.

I like being able to search, get my quality results, and move on with my life. That's worth paying for to me.


A contract isn't a subsidy... A subsidy would be giving them dollars without any particular strings attached except perhaps to use those funds to develop the product. If the contract is to provide money in exchange for services, that's called a transaction.


I see it differently: for example the fact that the US government spends a lot of money on military can in my opinion clearly be called a subsidy for the military-industrial complex.


So then if the government buys pens and reams of paper, then it's the government subsidizing office supply stores? But it's not a subsidy if a corporation spends money on the same supplies?

My employer does business with the DoD and with private corporate entities. Both the government and the private sector spend the same money and receive the same products and services. I appreciate that you have a different perspective, but I have a hard time considering my employer "subsidized by the US government" just because the government purchases our product.


> So then if the government buys pens and reams of paper, then it's the government subsidizing office supply stores?

If the government is a particularly important customer: yes.


Do you have a different term you use for when the government is not simply a customer, buying what they need, but intentionally funding a company in excess of the goods and services it receives? This would be more in line with the traditional definition.

I think a company can make 100% of its revenue from the government, but that doesn't mean it is subsidized. The critical criteria is if the government is directing funds for reasons other than pure procurement, such as buying votes, stimulating jobs, ect.


Location: San Jose, CA, US Remote: Open to it Willing to relocate: Yes Technologies: VMWare, Proxmox, KVM, Docker, LXC, Kubernetes, Terraform, Pulumi, AWS, GCP, Azure, CircleCI, Jenkins, Okta/OneLogin/Entra, SIEM, vulnerability management, Windows Server, Linux, many more. Résumé/CV: https://scarlow-my.sharepoint.com/:w:/g/personal/me_scottcar... Email: me@scottcarlow.com

I'm probably not the typical resource someone may scour HN for, but it can't hurt to throw my hat in the ring!

I'm a senior-level IT Infrastructure Engineer. I've spent the past 8 or so years helping startups transform their early-stage IT, slapped together with duct tape and glue, into enterprise-grade scalable systems and processes. I've seen startups through numerous SOCII and ISO 27001 audits, penetration tests, NIST 800-171 assessments, and FINRA audits. I've migrated on-premises workloads in the cloud, built a businesses entire IT infrastructure (office networking gear excluded) to the cloud. I've even worked hand-in-hand with DevOps teams to improve and troubleshoot CI, engineering access to backend services, and IAM architecture. And I loved every minute of it.

That's why I'm posting here on HN; I like a fast-paced environment where I can re-imagine how things are done!

My linked resume is for leadership, as I've recently made that shift, but nearly my whole career is as an IC and my accomplishments in my resume are overwhelmingly accomplished as an IC or small team lead. I'm happy to be an IC again for the right opportunity.


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

Search: