HN user

jammi

66 karma
Posts2
Comments65
View on HN

Thanks, I converted it into a Tampermonkey userscript to use on all the sites.

  // ==UserScript==
  // @name         Underline links
  // @namespace    http://tampermonkey.net/
  // @version      0.1
  // @description  Underline all the links!
  // @author       mdaniel
  // @match        https://*/*
  // @match        http://*/*
  // @grant        none
  // ==/UserScript==

  (() => {
      document.querySelectorAll('a[href]').forEach(it => it.style.textDecoration='underline');
  })();

Are knobs and plastic moldings that expensive though?

Yeah, the molding for any typical single component is tens of thousands of dollars per iteration. A car has a lot of those components, so the fewer the better.

The main issue with it is that it's too good and successful, therefore it's too easy to publish whatever crap as your library or its dependencies.

That's not really a fault in the tool managing installation and publishing the library, its dependencies or managing the repository, providing the auditing system, script runner frontend and the other things npm does.

You could similarly argue github is hot garbage, because there are so many crappy projects hosted on it.

I don't believe yet another package manager is going to fix anything, more likely it'll take years to reach maturity, will be riddled with bugs until then, and have some serious fundamental issues on its own that will be revealed down the path, if it ever gains popularity.

Don't fix it if it aint broke should be a motto for more developers. Settling for good enough prevents second system effects and retards immaturity in the form new "trendy" products that over-promise and under-deliver solutions.

Nothing is perfect, but replacing something from scratch because of some mostly irrelevant issues that would be better handled by improving the standard solution usually just causes more issues than it solves.

Probably worth it, since he got a MacBook Pro a year earlier than everyone else. For the rest of us, the MacBook Pros (started as the short-lived Core Duo models) weren't available until spring 2006. The Core 2 Duo models didn't exist until late 2006.

MacOS Marzipan 8 years ago

I feel like it's similar to the skeumorphism of the past coming back with a revenge.

Not only does materials overall matter little, but Lithium is also super cheap compared to the other materials in the batteries. There's a lot more of Nickel in a Li-Ion battery and it's much more expensive per volume and weight as well.

The batteries would be called Nickel-Carbon or something like that rather than Lithium-anything, if they were named by the amounts or costs of materials in them.

I'd also say a large part of its issue is lack of internal consistency of the format itself. Firstly there are the various official RSS versions, then there are all those Atom things and probably others as well, and then there's the thing about how you're supposed to render the things correctly. XML as the content format is also pretty much antiquated.

A modern format would no doubt have to be JSON- or YAML-based and have its human-readable content in plain text or markdown, so it'd have to be pretty much readable with a plain text http client, like curl.

So, just let RSS die the slow death it's been going through for good reasons and bring something consistent and straight-forward into its place. Something that you could easily generate and parse from any modern language without specific libraries.

Bringing RSS back is like trying to bring SOAP as a RPC system back; it just won't fly anymore no matter how much hot air you try to pump into it. We know better now and have better ways to do the things.

The copyright compensation on electronic books is different from paper based ones. The super greedy licensing deals (where even available) is one of the things that hold back electronic books; they're simply much more expensive than paper-based ones. The Finnish libraries do have e-books, but they're not as common to loan as paper ones are, and not everything is available in e-book format.

Seems like an article from a paper romanticist, and they aren't extinct yet. Anyhow, here in Finland the libraries are not just for paper-based information storage/dispersion, but common places for all kinds of public information/technology needs, like (3D) printing, copying or digitizing material into modern formats, and free guided computing needs for poor or old people. They're also public gathering places, including their conference rooms you can lend, which is also nice for startups without their own offices and such. In any case, they'll have uses far beyond the age of paper-based media, including uses we can't fathom yet.

The problem is that the average salesperson is pretty ignorant, even about the probuct he's supposed to sell and the target audience to sell to. Encountering a great salesperson is a rare occurrence in life, encountering a more or less average one is very common.

Oh right, the mobile app auto-corrected EU to Eau and didn't reply to the context I clicked in. So, any iOS apps to recommend? The "Hacker News" one apparently sucks for commenting.

In EU countries they should be classified as light electric vehicle or something like that, along with things like skateboards, rollerblades and “hoverboards”. Hence, allowed basically wherever pedestrians are allowed, unlike the bigger and heavier mopeds and bicycles. At least this has been the case in Finland since the newest Eau directives of the sort were ratified.

Experience first-hand or via experts who repair them daily, the former can be done by owning the same car or brand for a longer while and spotting the pattern.

Prefer makes that have excellent rust protection and models with relatively low stress configuration engines rather than high performance models. The two latter are usually mechanically the same or mostly the same, but the latter of them receive much larger stresses in use and hence tend to fail earlier.

If you intend to modify the car, prefer older ones, because they have lower regulations, but this depends on the legislative area you are in as well. For instance cars with OBD-II are too new for engine upgrades almost anywhere.

Happens with the better ones as well, it's just a matter of setting the torque limiter of your screwdriver/coordless drill to match the job. Sometimes takes a few mistakes, but it's safer to start with a low setting and adjust up until you have the right torque for the screw.

Yes, if maintained properly, which means swapping out these engineered to fail parts every so often, which becomes uneconomical at least in the resale sense at some point in time, because the repaired car resale value is less than the cost of repair. For instance on VAG cars, the designed to fail cash-cow parts are typically the various suspension bushings. Once such a part is worn out, resulting in a part that has excessive backlash, it'll cause prematurely worn out parts in the rest of the system it's a part of as well.

My daily driver is a 25 year old car that I'm keeping on preventive maintenance. I got it when it was 16 years old and still in pretty good shape since it was barely used and always kept in a warm garage. I've always had pretty old, but well maintained cars in order to minimize the total cost of ownership of them, and kept them running until something too difficult or expensive breaks. I never value them for what I'd get for selling them, because I've never sold a car nor planned to. To me, the car value is always the utility and TCO value of knowing the state of them via preventive maintenance repairs. Usually the failing part not worth fixing is the body, either due to a collision or rust damage.

In addition to always inspecting an used car from underneath, a thing I learned early was to replace all the cash-cow OEM parts with upgraded parts when possible. If not, at least try to have repaired parts made that are improved at the point of failure to be stronger than OEM parts, so that they don't fail the same way again. Factoring the preventive repair into the price of the used car is required in order to be sure to afford owning the car. After that initial preventive repair, it's about checking the parts stay like new, or it becomes very expensive to keep very quickly once something fails after a part's worn out.

Anyhow, look at farm equipment, mine equipment and such to see what vehicles not engineered to fail are constructed like, and I don't mean the extra robustness of the loadbearing parts for the much larger workloads they're designed for.

The only real reason for Phillips screw heads were the old electromechanical industry robots that would rely on auto-centering and spring tension to pop the driver out of the screw against a switch at the set torque. Modern (since 1980s or so) industry robots are computer-driven and torque-sensing. Phillips (and Pozidriv) needs to die in favor of modern superior screw drive designs like Torx.

Robertson in Canada is just appeal to tradition at this point. They have no technical merit over Torx except maybe ease of ad-hoc construction of a driver.

They do. Cars are engineered to fail and some models are sold even at loss to get the profit from OEM parts and service. This is also often the reason why seemingly similar parts are incompatible from one model to the next; the manufacturers are racing against the (often much more durable) aftermarket parts. If they were in the business of making cars great for the consumers, they'd engineer them strong with grease fittings on every moving joint and have all parts standardized across models and brands, differentiated mostly by car size or such (supercompact vs crossover suv vs heavy-duty truck). This would however result in cars that would be easily maintained to last forever, like some old work equipment is and that'd be bad for the planned obsolescence market model of car manufacturers.

As an entrepreneur and software consultant, it's more of a "make the good people pay". Here any improvements made must be obviously useful to be worth the money. I'd redefine it like this, where usefulness is the prime motivator:

1) Make it work, if that's important and worth the time

2) Make it correct, if that's important and worth the time

3) Make it fast, if that's important and worth the time

Most of the time is spent hunting for what the software is supposed to be. Prototype, prototype and prototype until you get even close to what it's supposed to be. Treat everything as temporary until then, before applying any real importance on any of the above. Even then, you'll rather be rewriting it anyway, focusing on what's important, because your assumptions at the beginning were most likely wrong. You shouldn't hang yourself for those early decisions just because you invested too much time and effort on making them work.

How about this? There are also plenty of DOS PC-speaker-savvy demos from the 90s on pouet.net and scene.org, but there are apparently no recordings of them on youtube without sound card configurations. Some of the late DOS games also had awesome PC-speaker support. There was also a Windows sound driver for the PC speaker in Windows 3.1 times, maybe Windows 95 as well. Basically; the faster the PC, the higher the sampling rate you can go. The sound output on Raspberry Pis and some of the cheaper USB sound cards are also very similar to having stereo PC speakers, since that's also about just dumb bit-banged PWM.

https://www.youtube.com/watch?v=dV1EMcH316s

Just like in combustion engines, it seems like the best things are held to the last generations of hardware. I expect both to lose market share down to nil during the 2020s. BEVs replacing internal combustion engines and solid state storage replacing HDDs even in cost per storage unit.

A PC beeper can sound just as good, when used on a fast enough PC and the beeper output is connected to something better than the built-in piezo speaker. Even on the original IBM PC, you could make it sound almost as good by very careful optimization and close to 100% of allocation of CPU cycles, like shown at the end of the 8088 MPH demo: https://youtu.be/hNRO7lno_DM?t=6m52s