wmanley

15 ms·

151.
by wmanley 5y ago
Author here. I thought I'd post this since "Reproducible builds for Debian"[1] is being discussed on the front page. I wrote apt2ostree. It applies the cargo/npm lockfile idea to debian rootfs images. From a list of pac
152.
Lockfiles for packages in a Debian/Ubuntu rootfs(github.com)
3 points by wmanley 5y ago|1 comments
153.
by wmanley 5y ago
On the subject of reproducible debian-based environments I wrote apt2ostree[1]. It applies the cargo/npm lockfile idea to debian rootfs images. From a list of packages we perform dependency resolution and generate a "lockfile&qu
154.
by wmanley 5y ago
There's a sentence in here that really gets to the value of AWS for businesses: > So while your customers and employees are going to be mad, they’re also going to be distracted from worrying about your downtime. This is incredibly i
155.
by wmanley 5y ago
$ python2 -c 'False = None = True' File "<string>", line 1 SyntaxError: cannot assign to None $ python3 -c 'False = None = True' File "<string>", line 1 Syn
156.
by wmanley 5y ago
> Trailing commas are also nice to have - although we have linters for that, unfortunately some people think they're too good to need a linter. IMO the real value in trailing commas is that it's easier to produce simple JSON pr
157.
by wmanley 5y ago
You can apply this to any interaction where you have to wait for a round-trip anyway. It saves you coming up with a JSON schema and endpoint for the request, and then gluing it all together. It doesn't mean that you don't use jav
158.
by wmanley 5y ago
This sounds like an optimised implementation of the design described in "The Future of Web Software Is HTML-over-WebSockets": https://alistapart.com/article/the-future-of-web-software-is... HN discussion: ht
159.
by wmanley 5y ago
See also some background in this LWN article: https://lwn.net/Articles/847412/
160.
by wmanley 5y ago
> It is reasonable to specify your domain closely, otherwise you end up with sqlite It seems like you're trying to use SQLite as an example of something you don't want to end up with. This seems backwards so it weakens your a
161.
by wmanley 5y ago
The point was that these were either dismissed or weren't considered by Kay when describing breakthroughs in computer programming. They aren't breakthroughs in computer programming languages, but IMO are breakthroughs in computer
162.
by wmanley 5y ago
I feel like Kay has taken a rather too narrow view of what counts as programming. IMO here are the breakthroughs in the last 20 (ish) years: 1. Stack Overflow - search for your problem, copy and paste the answer. 2. git - Revision control t
163.
by wmanley 5y ago
Here's my solution: def monotonic(it): run = [] for this in it: if not run: pass elif run[0] < run[-1]: # Increasing if this < run[-1]:
164.
The Raspberry Pi as a Stratum-1 NTP Server (2012)(satsignal.eu)
68 points by wmanley 5y ago|34 comments
165.
by wmanley 5y ago
> * Most users without hardware accelerated WebRender will now be using software WebRender. > * Improved software WebRender performance This sounds interesting. Does anyone know where I could read more about this?
166.
by wmanley 5y ago
See also: Ghosts of Unix past, part 4: High-maintenance designs: https://lwn.net/Articles/416494/ > While hard links are certainly a lesser evil than setuid, and there is little motivation to rid ourselves of t
167.
by wmanley 5y ago
Where do you get the electricity?
168.
by wmanley 5y ago
See the next article in the series "Ghosts of Unix past, part 4: High-maintenance designs"[1]. This specifically addresses how the existence of hard links is elegant in itself, but exports complexity to other parts of the system.
169.
Ghosts of Unix past, part 3: Unfixable designs (2010)(lwn.net)
167 points by wmanley 5y ago|75 comments
170.
by wmanley 5y ago
On the subject of signals and other problems with UNIX I can recommend Neil Brown's Ghosts of Unix past, part 3: Unfixable designs[1] [1]: https://lwn.net/Articles/414618/
171.
by wmanley 5y ago
I think the point is that while CPUs have gotten (significantly) better over time using a computer doesn't feel any faster than 10 years ago because software has more than made up for it. On my 3 year old Ubuntu machine here it takes
172.
by wmanley 5y ago
No. If we accept your argument then this would be correct: > In absence of a standard effectively every language construct is 'implementation defined behaviour'. But the parent said: > In absence of a standard effectively ev
173.
by wmanley 6y ago
What you seem to be describing is "unspecified behaviour" or "implementation defined behaviour". If your program contains undefined behaviour the compiler makes no guarantees about how your program will behave. For more
174.
by wmanley 6y ago
Yes please. I've often thought the same. Mentioned this comment here: https://blog.williammanley.net/2021/03/31/seen-on-hn-invert-... You’d need to implement a new protocol between terminal and shell. Ma
175.
by wmanley 6y ago
> To me this idea sounds a lot like "why do we need IPV6? Why not keep IPV4 and add a few bytes?" except it's effectively almost the same amount of breakage. [DJB disagrees]( https://cr.yp.to/djbdns/ipv
176.
by wmanley 6y ago
> Well, as soon the solution doesn't scale - which will likely be within a couple of years - one needs to rearchitect and recode. Your project is far more likely to die within a couple of years from having too few users than from ha
177.
CVE-2021-3156: Sudo privilege escalation(cve.mitre.org)
34 points by wmanley 6y ago|4 comments
178.
Unlock software freedom one by using better tools(blog.williammanley.net)
3 points by wmanley 6y ago|0 comments
179.
Source Code Linking: Merging C Headers into Rust Modules(immunant.com)
79 points by wmanley 7y ago|6 comments
180.
by wmanley 7y ago
Hacker news discussion of previous article in this series: https://news.ycombinator.com/item?id=20738606 Discussion of this article on the rust subreddit: https://www.reddit.com/r/rust/comments&#x2

More ›