> macOS machine (which is BSD-like enough down below)
That's like saying an Ubuntu .deb will work on Gentoo because it's all Linux anyway. It's not that simple. There is dependencies and there are differences in the packages, package managers and surrounding system for a reason. It's not 1:1.
Perhaps the naming scheme happened to line up for the packages you where using, but this should be considered not assumed.
It would be nice if there was some sort of translator that could handle "most common cases". I think it would improve the usability of Jails.
Perhaps that would require someone to keep a list of packages mapping certain packages between operating systems.
Something like "apt install python3-serial" -> "pkg install py311-pyserial" may suffice.
For anyone that would use something like that, you should implement a prototype, publish it and perhaps someone else will build upon what you started!
Maybe it's just me but what happened to "don't send your government id to anyone". I am from the EU but this is what was indoctrinated to me. Just seems very strange to all off a sudden send all this information to any company you require a service from.
Also the person is not the company, why is Google making the developer identify oneself while many apps are released under a company? My understanding is that Google has been mishandling this for a while but with the verification linked to a government id that just seems like another can of worms.
A few scenarios to consider:
- The developer is fired/resigns and the company does not want to be associated with the developer, for example if the developer is convicted for something.
- The developer is fired/resigns and the developer does not want to be associated with the company, developer found out about certain practices of the company they don't condone.
- The developer and the company part in good faith, however one of them is being exploited/pressured by a third party to abuse the relationship to the app.
- The developer or the company is on legal hold due to legal issues, arrests, malpractice etc.
- The developer passes away or the company ceases to exist.
- How does this work if you are making an app as a developer for hire, when entering into a contract with a publisher for example. Who will verify and how will that work (especially on small scale apps).
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.
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.
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.
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.
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.
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.
Also the site doesn't even work well and is one of the main examples of "dark patterns" on the web [1].
Literally one of the worst companies and websites out there. Stallman has a summary of the additional reasons [2].
[0] https://www.eff.org/deeplinks/2017/12/eff-court-accessing-pu...
[1] https://medium.com/@danrschlosser/linkedin-dark-patterns-3ae...
[2] https://www.stallman.org/linkedin.html
reply