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

> No, that's "ancient regex".

wouldn't the "ancient regex" be the ed "g/re/p" version?

  -E, --extended-regexp
    Interpret PATTERNS as extended regular expressions (EREs, see below).
  -G, --basic-regexp
    Interpret PATTERNS as basic regular expressions (BREs, see below).  This is the default.
  -P, --perl-regexp
    Interpret I<PATTERNS> as Perl-compatible regular expressions (PCREs).  This option is experimental when combined with the -z (--null-data) option, and grep  -P  may  warn of unimplemented features.
From the manpage it seems my grep make distinction between "Extended" "Basic" and "Perl" regexes.

>wouldn't the "ancient regex" be the ed "g/re/p" version?

That's "prehistoric regex"


Funny idea and it may make sense in some special scenarios.

However I would like to point out that you are limited to path and filename length.

Maximum file path length in Windows is 260 characters. (32767 characters with longpath enabled). Individual filenames max out at 255 characters.

Maximum file path length in Linux/Unix generally is 4096 characters. On ext4 it seems max filename length is 255 bytes.

Additionally you will be constrained by the characters allowed in files. Therefore it will be strange to pass a filepath to a program like this.


That's what directories of files are for. The file system as a cognitive twitter.

I may interpret this wrong, but the 9p protocol describes transfer protocol operations not data structure.

9p defines filesystem operations: attach, walk, open, create, read, write, clunk, remove, stat. And some additional handling operations: version, auth, error.

This project replaces those with RESTfull (CRUD?) operations. But this repository also seems to define what 9p does not, the structure of the data. It defines what files to write to and what to write to them. That seems outside of the 9p scope as you are defining the service behind the transfer protocol.

A RESTfull API to attach to a 9p backed does seem useful since the support for RESTfull API's is so huge. To me it's unclear how this monolithic approach is beneficial above a "RESTfull to 9p" proxy and a 9p service.


Modern (suburb) SUV's spectacularly suck at most tasks, you have been falsely advertised to.

A 2010 Toyota Corolla is most likely a better offroader, a 1.8t VW Passat is a better tow truck.

If not for the tax benefit these SUV's enjoy they are useless.


I think in this case the point being made is "bad software makes the whole product bad", not just "bad software is bad".

Its similar to how bad brakes or a roof prone to leaking makes the whole car a bad car. The "weakest link" undermines the whole system.

> software isn't the core competency

Software is a essential part of modern cars, remove the software and they don't function (or in some cases are not allowed on the road). The car manufacturers "core competency" is making cars so I would argue that software is definitely a "core competency" of a modern car manufacturer.


I agree it ruins the whole product.

I also agree traditional car manufacturers should have software as a core competency, but instead they're notoriously terrible at writing software.


Because you can choose to leave your phone at home and are travel everywhere by car if you don't want to be tracked. But you can't leave your car at home and travel anywhere.

It is true that we don't need cars sending telemetry to track us since there is a conveniently placed identification number on the front and rear of the car, the number plate (used by government), but this is physically broadcasted and that limits its reach.

So why should the manufacturer of my car have access (and the right to sell) a lot of my personal data like location, weight, age indefinitely just because I own a product manufactured by them?

It is an unnecessary overreach on very sensitive data and I can't really opt out (if buying a modern car) since all manufacturers are doing it.

Yes I also carried a phone everywhere the last 20years, but that doesn't make the tracking right (also on phone I think we should be tracked less).


I understand and agree in general, but the root issue is in the laws and what's permitted to companies. Giving your data to car manufacturers and 3rd parties should be mandated to be disabled by default by law and only enabled with proper informed consent.

This could be but in practice it doesn't work.

Both the governments and the manufacturer benefit from you driving a newer vehicle instead of keeping your old car running. Topics like environmental impact safety etc. are higher priority compared to repair-ability. Additionally most people don't care.

Additionally there is the issue of licensing and regulation around the hardware and software of a vehicle. The regulation in my country is written around "type approval" and this means you can not change the car significantly beyond what is approved during the car "type approval" process.

On top of that this market is ripe for abuse of planned obsolescence as the product is very technically complex and there is no real regulation against it.

This is why I drive an old car and a simple modern car, most modern smart tv's with wheels strapped to them will become bricked the moment the manufacturer doesn't support them anymore (after the 10year lifespan).


In my experience, it does actually work. Tesla model s had an issue with the flash memory endurance, and the NHTSA made them replace it. Which they did, and upgraded the 3G modem to LTE while they were at it. My 2013 Model S is still going strong, still gets software updates.

> the NHTSA made them replace it

They forced them to replace it because it was recognized as a manufacturing/design defect. This is a very different scenario from "normal wear" replacement.

Additionally the Tesla model S is still in production with only a facelift. Therefore the parts that are produced are not unavailable (or not supplied).

I think you can't replace/upgrade the flash and modem yourself without the assistance of a Tesla dealer.


> We're not talking about gambling-as-addiction.

What makes you think this is not "gambling-as-addiction"?

It seems to me that these players, big or small, either have too much skin in the game or are compulsive gambling. To me the threats only make sense in that context.


One of the things I don't get is the economics of these trackers.

Someone is serving this amount of data to every visitor. Even if you want to track the user as much as possible, wouldn't it make sense to figure out how to do that with the least amount of data transfer possible as that would dramatically reduce your operating cost?

Perhaps size optimization is the next frontier for these trackers.


Traffic for the static payload is super cheap. And the insane amount of requests is handled easily by modern event-based architectures. The operation costs are most likely only a tiny amount of the overall economics of the tracker's buisness model. The generated tracking data is certainly worth an order of magnitude more then it takes to generate it.

you may be able to use the "ctrl (⌃) + cmd (⌘) + space" (character viewer) menu to select it? There may also be another shortcut for it.

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

Search: