I'm not saying I'm for those over open source licenses in general, but Prusa brought up some fair questions when discussing the OCL. Essentially: define "personal use." Have I violated a non-commercial license if I print this keyboard and then use it to build someone a website? Does CC-NC mean a Prusacaster -- or any guitar knob with such a license for that matter -- is strictly barred from being taken on tour? Or used to record albums that are then sold? (And I say "guitar" knob, but I'm choosing an example a little consciously that could exist in any variety of controls, instrument and otherwise.)

Where are the lines of that when it's physical things? How far downstream does that go if it isn't CC-NC-SA in particular?

I'm not really sure that Creative Commons had the idea of physical production in mind, given that it dates back to a time when we were more broadly talking about digital piracy, and I honestly haven't kept up with its evolution much in more recent years. But maybe it just doesn't make the same sense for designs of physical things, for comparable reasons to why it wouldn't make sense for code -- and, conversely, open source projects that opt to use CC licenses for assets.

(None of this would stop me from attempting to build/mod one for fun, mind you. It just raises what a more averse person might call risks, and what I will at least call curiosities.)

Whereas in more recent years, keeping a closed-source rendering engine that was no longer competitive in implementing the spec, wasn't being used when people had a choice, and was being used as a dependency for core components of the OS, probably wasn't winning many arguments.

(Edit: yes, I know Chakra was open source. I meant Trident.)

Everything from Edge as a cross-platform Chrome derivative to .NET as a cross-platform open-source toolkit to their React Native builds and experiments with Android suggest that MS itself understands this. The Linux side demonstrates it with things like Proton and the forthcoming Android desktop mode. The Web demonstrates it in general as it expands in capability and more applications skip shipping native entirely in favor of technologies like Electron. And not that I don't personally sob in system RAM, or have extreme reservations about how we got these things (see: Google and antitrust), but I can't say I hate the ease of switchover.

Ecosystem lock-in didn't go away, but it feels like it's changed a lot.

[1] https://arstechnica.com/tech-policy/2023/02/report-musk-had-...

Doesn't seem like that much of a stretch from a UI perspective to do something similar with a Markdown preview.

Though I don't really have a system for storing them effectively as of yet, and as someone with a strong preference for open source on my critical workflows, I never got on the Obsidian train myself. Current experiment is Silverbullet.md, because I do very much like raw Markdown and file-based notes, but that's different from having a meaningfully fleshed-out setup haha

Points: 5

# Comments: 2

This is easily one of my favorite descriptive details I've ever seen in a README.

> Inspired by (and in joyful dialogue with) motherfuckingwebsite.com, justfuckingusehtml.com, bettermotherfuckingwebsite.com, and justfuckingusereact.com. Extremism in defense of developer experience is no vice! This site made by me. Does this all sound a bit like shallow slop? Yup, please help make it better.

I agree with you, and wrote a similar one for Markdown that you might enjoy. Same overall naming scheme. (Note: open the comments before you judge the use of a Web Component for rendering purposes.)

(I mean, that could still steer it toward places that have affiliate programs, but if you're running a local AI tool to help you search for these things that seems like something you should reasonably be able to toggle on and off/configure in a system prompt/something.)

RISC-V was developed at UC Berkeley. It's roughly as Western as West realistically gets, short of being made in Hawaii.

> That's a geopolitical question

Sure, but that's not actually about where RISC-V is from. It's that it's a purposely open platform -- so much so that its governing body literally moved to Switzerland.

The reason it's a geopolitical question is more to do with what we did to their supply chains with sanctions on companies like Huawei and ZTE, and what COVID did to everyone's supply chains independently of that. Both of those things made it really evident that some domestic supply chains are critical. (On both sides -- see: the CHIPS Act)

Where RISC-V comes back in is that open source doesn't really have a functioning concept of export restrictions. Which makes it an attractive contingency plan to develop further in the event of sanctions happening again, since these measures can and have extended to chip licenses.

(Edit: I'm not saying any of this is mutually exclusive with valid concerns about Huawei, raised by various other sources. I'm less familiar with ZTE's history, but my point in either case is more of a practical one.)

There was that time Zuck made a bad bet on VR and then the entire dept working on it got slashed...

Layoffs, by definition, aren't about individual employees.

Comments URL: https://news.ycombinator.com/item?id=45429403

Points: 2

# Comments: 0

github: [username]/escape-rope, /escape-rope-ui | UI demo: escape-rope.bhmt.dev

Personal side project: extensive cleanup of my family's place. I'm just now approaching a decent first pass at the outside, and have to tear apart a basement next. It's taken most of this year. It's not the specific reason I've farmed collecting search results off to a bot

For-fun thing: CTF puzzles. I'm not very good at them, but they're useful for other things. I fell down the scraping rabbit hole this way, and I'm currently using a series of them to finally get some exposure to Python. I also have a writeup half-written about this exact process