Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pbar
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
pbar
8mo ago
Unfortunately with SSH specifically, the dissectors aren't very mature - you only get valid parsing up to the KeX completion messages (NEWKEYS), and after that, even if the encryption is set to `none` via custom patches, the rest of th
2.
▲
Nix-mdbook: Flake for building mdBooks
(github.com)
2 points
by
pbar
1y ago
|
0 comments
3.
▲
by
pbar
2y ago
Was it intentional to reply with another no true Scotsman in turn here?
4.
▲
by
pbar
2y ago
Ah, quick and painless then
5.
▲
by
pbar
3y ago
It’s all fun and games until your KDC goes down!
6.
▲
by
pbar
4y ago
Interesting, what were some of those unique optimizations?
7.
▲
by
pbar
4y ago
It’s a spreadsheet world and we’re just living in it ;)
8.
▲
by
pbar
5y ago
To their point, S3 buckets must be uniquely named globally, across all of AWS
9.
▲
by
pbar
6y ago
It’s always surprising to folks, but true, that Houston has a wealth of arts/culture/dining, and even a modicum of public transit (the metro rail, heh). Entertainment could be better, but the rest blow Austin out of the water!
10.
▲
by
pbar
6y ago
Single responsibility - that same container is gonna get shipped to prod/etc. I would hope the database isn’t in the container there!
11.
▲
by
pbar
6y ago
I get your point, and I disagree on opinion. I and many others have had success using containerized devenvs on projects both large and small, and have likewise felt some pain with respect to repeatability when not - especially with the Pyth
12.
▲
by
pbar
6y ago
This kind of thinking is why engineering departments have tech debt.
13.
▲
by
pbar
6y ago
Another counterpoint to readability: the benefit is diluted if the reader isn’t familiar with the dependencies. I know this goes both ways, though in some circles (say, devops) there’s more familiarity with Unix tools than Python. So the co
14.
▲
by
pbar
6y ago
In a similar vein, you also pretty well ;)
15.
▲
by
pbar
6y ago
To each his own. There is an equally wide group of developers who choose Go for personal projects as it’s in line with their taste. The joy of programming is in the eye of the beholder.
16.
▲
by
pbar
6y ago
The frustrating part is, I definitely faint due to blood being drawn for example, but something about the sight of the procedure makes it hard to look away
17.
▲
by
pbar
6y ago
The reality is that containers via `runc` really _are_ just bundles of processes with some sugar to control Linux namespaces. Using another runtime (kata, etc) would get closer to the tighter abstraction you mention, but it would truly be a
18.
▲
by
pbar
6y ago
That’s not edgy enough for HN ;)
19.
▲
by
pbar
6y ago
And interrupt their mostly nontechnical employees’ productivity to learn a new OS, for a negligible cost savings? Good luck getting that past a board of directors.
20.
▲
by
pbar
7y ago
We have to remember the Fermi Paradox is a Fermi estimation and only that
21.
▲
by
pbar
7y ago
This is the same case regardless of being in a container or not, $app v0.1 and $app v0.2 will have different filters
22.
▲
by
pbar
7y ago
From a developer point of view, one should not have a mental model in play for Kubernetes, the standard 12 factor pattern should be it. If not, the infrastructure and the app are strongly coupled
23.
▲
by
pbar
7y ago
Make sure to take great care of the monorepo, and break it up _before_ it becomes impossible but necessary
24.
▲
by
pbar
7y ago
Agree totally. One win Kubernetes provides my current team has been the fact that it is the interface on top of a cloud with agnostic primitives, allowing for multi cloud scaling. There are a lot of primitives, and a lot of things to monit
25.
▲
by
pbar
7y ago
A process making a system call to the kernel functions the same way regardless of whether it is in a container or not. How exactly does the security model differ at all?
26.
▲
by
pbar
7y ago
You might find the Kubernetes offer interesting. Pod Security Policies[1] expose seccomp and selinux configuration in the form of annotations. [1]: https://kubernetes.io/docs/concepts/policy/pod-security-poli.
27.
▲
by
pbar
7y ago
I wonder about similar future change in imagination. Almost certainly possible since there's precedent for it happening, but the hard part is imagining what sort of thought it would enable.