dozzie

10 ms·

31.
by dozzie 8y ago
Everything is a file... except processes (you can't just delete a process), network interfaces (try setting an IP address with a write() or ioctl()), and plenty of other things. Unix never had "everything is a file" as its ma
32.
by dozzie 8y ago
The word you were looking for is "craft".
33.
by dozzie 8y ago
> [...] to any one in any other regulated industry this sounds crazy. This sounds crazy even to a person who makes living from running software on commodity hardware (x86/x86_64). Android does not sound like a hard real-time OS. I&#
34.
by dozzie 8y ago
And what exactly is wrong about that? Its loading and rendering speed? Or that it works in text mode?
35.
by dozzie 8y ago
> AUR never tried to pass false sense of security, it is explicitly declared as not supported everywhere. Funny that I only ever hear of this when talking about security aspects, not when discussing available software. In the latter case
36.
by dozzie 8y ago
Start writing tools for sysadmins. Think of all the times when you hit a wall because there was no inventory database that could be queried from command line , not just browsed through a web UI, or when you wanted to coordinate several bac
37.
by dozzie 8y ago
> It's an important distinction because if the software isn't at fault, [...] Though the software is at fault. It created a false sense of security, misleading the users. What else in Arch just feels secure, but in fact is not?
38.
by dozzie 8y ago
Oh yes, it is a problem with the users, not the software itself, but you don't get to separate the two in the case of an OS or distribution.
39.
by dozzie 8y ago
Which, as I said, very conveniently is glossed over by Arch users.
40.
by dozzie 8y ago
The thing is not that it's a new deficiency or something, it's just that Arch user conveniently ignore this when praising their distribution over e.g. Debian.
41.
by dozzie 8y ago
> Isnt the entire purpose validation of data? No. Digital signatures are for validating the data (who said what). The whole purpose of blockchain is to tell who said what when . Document timestamping, in other words. There were previous
42.
by dozzie 8y ago
Remember that your solution should be simple to deploy, so it can be useful in a small scale. And remember not to write it to run under Docker. If it is Docker-only, you cannot use it without it, and not everybody has or wants Docker. Keep
43.
by dozzie 8y ago
Ah yes, this totally separate journald that you can replace with something else, except that you cannot, you can only run it in forwarding mode beside other logging daemon. Very modular. Totally not a part of an init system.
44.
by dozzie 8y ago
QR code generator is not a common feature of an init system, yet systemd includes one. Modern attempt at OS packaging (a.k.a. containerization) is not a weird thing in such a neighbourhood at all.
45.
by dozzie 8y ago
It's not an alternative to PDF. It's an alternative to Kindle's MOBI. PDF is intended for printing, and ePUB with its XHTML and CSS has nothing that makes printing easy.
46.
by dozzie 8y ago
Yes, we are rare indeed. There's not much of a market for writing tools that work with the OS, developers usually want to stay away from the OS-provided mechanisms, like build and packaging systems, network configuration, event logging
47.
by dozzie 8y ago
> we break our python code into microservices so it is more important documenting the APIs rather the code itself. If you write libraries (and you actually do without microservices), you still need to document the APIs. No difference the
48.
by dozzie 8y ago
Heh, if only the hit chance was actually the hit chance. Very often the same attack, e.g. three strikes with 60% chance, yields something like 30% hits when the situation is repeated multiple times (save-attack-load-attack).
49.
by dozzie 8y ago
Ever heard of this silly thing called distributed hash tables? And BitTorrent protocol that is currently the most popular implementation, which sets up a whole DHT/P2P network for every share? There, as one example.
50.
by dozzie 8y ago
No, encryption is for keeping secret a secret, even if it ends up public. But this misses the point. Blockchain is an implementation of a specialized cryptographic primitive called "document timestamping". Nothing this primitive p
51.
by dozzie 8y ago
If you use blockchain for storing secrets, then you signal that you don't know what blockchain was intended for and what storing secrets needs, in other words, you signal that you are not competent to build a password store.
52.
by dozzie 8y ago
Note that you don't always need to be paid with money. You can demand a good liquor, a dinner, or a cake as your remuneration, depending on how big and difficult the work is. And while it may be ridiculous to offer or demand a mere twe
53.
by dozzie 8y ago
The main points mentioned in the article are: - our code ended up as entangled mess - we don't train our newcomers - we don't use staging environment, and instead we deploy directly into production - other teams for configuration
54.
by dozzie 8y ago
Hint: blockchain is a timestamping service. What is new compared to the body of research you speak of is that it doesn't need trusted third party.
55.
by dozzie 8y ago
> There are also Ports, which don't carry the same risk of fatal crashes. Oh, this is cute statement xD No, ports also carry the same risk as NIFs if you use port drivers , because it's still the same way of running the code
56.
by dozzie 8y ago
> [...] the idea of [...] writing native code that has a tremendously small likelihood of crashing is very appealing. Until recently, no such technology was available but Rust changed that. No such technology was available, barring maybe
57.
by dozzie 8y ago
It's really hard to design a programming language that does not revolve around APIs.
58.
by dozzie 8y ago
>>> REST is not intended to be a RPC protocol. Comparing it to one isn't appropriate. >> Ah yes, an obligatory reminder about this cute little original idea that never got implemented for computers to consume. > The w
59.
by dozzie 8y ago
> REST is not intended to be a RPC protocol. Comparing it to one isn't appropriate. Ah yes, an obligatory reminder about this cute little original idea that never got implemented for computers to consume. Though whenever somebody ta
60.
by dozzie 8y ago
OK, fine, then don't add it to the Depends field. But don't replace randomly things with a symlink to bash just because it's installed. If the scripts fail because /bin/sh is not bash, update your fsckin' broke

More ›