Not if you call it a student project! Probably your TCP/IP stack should not be someone's hobby project. A good threshold test: do you need to care about the license? If so...
I think we're making the same point really - I meant that it's not that OP's a student that means you might not want to actually use it for something, that just seems a bit mean/gatekeepy, but also naïve, to me.
I don't think there's any reason not to experiment with this any more than similar ShowHN hobby work from anyone else. i.e. follow its progress, maybe toy with it in your own hobby thing.
And honestly, I knew more about how to write a TCP/IP stack when I was a student than now. If I could do a better job now it would only be from some experience writing other code to RFC spec.
It's surprisingly good code for a student hobby project. I dipped in earlier hoping to find some silly gotcha to preen about, but it's well structured, follows a close read of the RFCs, and for its problem domain it probably needs to be in C anyways. I agree, the author shouldn't sell themselves short if they don't want to. But I also kind of took the "what's the license" question as a bit snippy, which I assume that preceding commenter did too.
Camneerg the machine, as well as the other systems and projects described within its pages have either ceased functioning, were dismantled, or given up on long ago.
No, but I also can't imagine Apple shipping something that needed a bodge wire soldered in to make it work well. They do a lot more power consumption engineering than most PC companies and they operate on such a large scale that they'd have found out about a battery drain like this much sooner and could fix it in the production process.
Yeah, it's not like they had any hardware defects like broken keyboards, power management issues, blank watch screens, recalled batteries, weirdly places antennas, etc... Oh wait they just ignore those until the problem gets large enough they get into news and need to start honouring the warranties.
Kind of missing the point, I think the above commenter was noting that they couldn't imagine Apple ever encouraging someone to get intimate with the internals at all. I certainly can't. You might say, "Why would you want to," but it's more about "why not?" I guess that's all a roundabout way to say that Framework is pretty in-touch with the hacker mentality, whereas Apple is too far gone in that respect.
You mean like when Macbook display cables were too short and disconnected if you opened and closed the lid often enough, and Apple denied there was ever a problem while fixing it a generation later?
In the US, this was the standard phone number to dial to connect to an operator-assisted (and later automated) information lookup, such as "get me the number of so-and-so in such-and-such city and state".
Personally I haven't needed to use it since probably the 1990s.
Expanding, US phone numbers are xxx-yyy-zzzz, where x is area code, y is prefix, and z is number.
It used to be that you did not have to dial the area code if you were calling a number in your same area code. So if your phone number was 415-591-0726 and you were calling 415-327-0914, you could omit the "415" part.
The prefixes ?11 were reserved: 911 for emergency, 411 for directory information, 611 for telephone company support, 711 for TDD / relay for the deaf, then 511 for road conditions I think, and then 811 for "call before you dig", aka please don't backhoe our fiber optics.
Many cities now also have a 311 service as a kind of non-emergency municipal call center for things like paying parking tickets or reporting potholes. My favorite use of this was in the early 2000s when it was used to trace the source of the mysterious "maple syrup events" in New York. People were encouraged to call 311 the moment they smelled the maple syrup odor and give the operator their location. By plotting the times and locations, they were able to trace it to a factory in New Jersey that was making artificial maple syrup flavoring from fenugreek seeds: https://web.archive.org/web/20190208102307/http://gothamist....
