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

Ive dabbled in a bit of all of this, and let me say, good luck! Sounds interesting.

Unfortunately, USB is hot garbage imo. The USB-IF, really screwed up USB, especially with all the power negotiation bullshit that has to happen now. Thanks to their ever changing USB3.x super premium plus ultra megaspeed crap that they keep doing, i ended up giving up on a multi-year usb project. Because of their changes, i would have had to change my entire build, and have to mitm usb devices, which i explicitly built my device to avoid. And then theres the USB-C cable, and the stupid process of negotiation and the power cable active crap, just... uhg, i hate usb after going down that rabbit hole.


Scientists and engineers have fantastic senses of humor when naming things.

> The time derivative of acceleration is called jerk, and the time derivative of jerk is called jounce. One published paper whimsically named the fourth, fifth, and sixth derivatives of "snap", "crackle", and "pop" after the cartoon characters on boxes of Rice Krispies breakfast cereal.


Hm, this is interesting. What kernel version did you find this in? Im curious if this is exposed to other languages

From the man page: Linux 5.14.

Before Linux 6.5, memfd_secret() was disabled by default and only available if the system administrator turned it on using "secretmem.enable=y" kernel parameter. [...]

"To prevent potential data leaks of memory regions backed by memfd_secret() from a hybernation image, hybernation is prevented when there are active memfd_secret() users."


That was tried, and what ultimately occured was disgusting.

The world was full of new computers popping up and every middle class or above person buying new ones like they do with iphones now. Companies started recycling programs, and many immediately went the route of corruption. They would pack up shipping containers full of ewaste, with 40-50% reusable items, and the rest junk, allowing them to skirt the rules. These containers would end up in 3rd world countries, with people standing over a burning pile of ewaste, filtering out reusable metals. There was, at one point, even images of children doing this work. The usable items were sold dirt cheap, with no data erasing, leading to large amounts of data theft, and being able to buy pages of active credit card numbers for a dollar.

We are talking about less critical things now, like vape pens, but its not a far throw for it to instantly become an actually bad idea to let other companies do the recycling. Make the manufacturer deal with it, or even the city/state, via public intake locations (like was mentioned of switzerland in another part of this thread)


Why past tense? That's describing exacty the world we are living in right now.

As far as i know a large portion of what i described shutdown after it came to light, although i would not be the least bit surprised if it was still happening in some capacity, or even in full under the disguise of something else

The downside to doing that is that their immune system would be weak in the end. We survive cold and flu because we have had them before, but someone going many years without the yearly viruses would get hit 100x harder, even potentially dying.

CL right now is like the best and worst place. Theres some good deals, from honest people; unfortunately, you have to wade through the scams sometimes though. Itd be great if there was better moderation, and we could find ways to bring it back to life that dont involve the awful things other companies do to survive

It's always been that way, and Markeplace is the same too. At least you can actually use search filters on CL, and it doesn't just show you whatever it thinks you want to see.

Took a quick glance through the code, its a pretty decent basic go at it.

i can see a few reasons for slowness - you arent using multiprocessing or threading, you might have to rework your rendering for it though. You will need to have the renderer running in a loop, re-rendering when the stack changes, and the multiprocessing/thread loop adjusting the stack as their requests finish.

Second, id recommend taking a look at existing python dom processing modules, this will allow you to use existing code and extend it to fit with your browser, you wont have to deal with finding all the ridiculous parsing edgecases. This may also speed things up a bit.

Id also recommend trying to render broken sites (save a copy, break it, see what your browser does), for the sake of completion


thank you for your quick code review and for these many helpful tips! I'll take a look at them and see what I can put into practice.

EDIT: Unfortunately, it seems that the code is getting near the limit of the context window for Claude, so I'm not able to add several of the feature suggestions you added with the present approach. I'll look into breaking it up into multiple smaller files and see if I can do any better.


You are definitely not a person i would hire.

You clearly dont understand that you dont get to make those decisions. Your users need software X to do Y as a business requirement. Are you going to tell them fuck off because you dont support windows? Sure, you could, once.

And no manager would ever okay someone writing a fuckton of driver shit or reverse engineering some protocols just so you can be high king and not use a specific OS.

Fact is business needs drive whats used, and you do not get a say in it, you might think you do, but you really dont. You can give information and options but ultimately it wont be your decision and youll support what the business needs you to support, or you wont be with the business anymore.

Yeah i agree vendors suck and so do license related shit, but you arent going to convince management that you could write a superior product AND support it for less than the cost the vendor would charge the company. And yes, this isnt always true, there are obviously some times when it is actually better to do it yourself, or use a foss solution. You still wont win in most cases. Users are going to use the thing they need and if youre blocking them from moving forward, youre more problem than the software youre trying to stop deployment of.


Man what the hell happened to imgur

I couldnt even see the images there, it was literally a whole page of ads


Aerospikes are hard because you cant control the external pressure. At altitude A you have X atmospheric pressure, but at altitude B, Y pressure, that pressure is what keeps the exhaust against the surfave and exerting force, you can only design an aerospike for a certain effecient operational altitude and outside of that its just not great.

A nozzle engine doesnt have to account for this as much because the nozzle is keeping the pressure of the exhaust


Nozzle engines absolutely have to account for the external pressure. The optimal pressure as the exhaust leaves the bell should be as close as possible to ambient for full thrust.

If the pressure at exhaust is higher than ambient, the exhaust pushes outward against the ambient pressure and you get huge exhaust plumes, and lost efficiency.

Conversely, if the pressure at exhaust is lower, the ambient pressure pushes the exhaust inward into shock diamonds[1] and you, again, lose efficiency.

Engine bells specifically yield their max efficiency at one external pressure/altitude. The reason you see shock diamonds is most often from ground-level testing (or takeoff) of engines that perform best at altitude.

[1] https://en.wikipedia.org/wiki/Shock_diamond


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

Search: