Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
froh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
241.
▲
by
froh
1y ago
it's complicated for appropriate values of complicated. more specifically it's defined piecewise and the standard then rounds some constants in the definition, which results in a slight discontinuity around the transition from one
242.
▲
by
froh
1y ago
> With C, you need a certain amount of skill. With a language like Rust that advertises memory-safety, they like that because it means you don't need as much skill anymore. this is a surprising statement --- in tust you need to form
243.
▲
by
froh
1y ago
then maybe amend your comment and start with " some of his grievances"?
244.
▲
by
froh
2y ago
TIL thanks for sharing!
245.
▲
by
froh
2y ago
nice to see they're in this too. https://news.opensuse.org/2025/02/18/rbos-project-hits-miles...
246.
▲
by
froh
2y ago
oh wow. were those context files? or did you write the multi page prompts by hand?
247.
▲
by
froh
2y ago
I think putting prompts into the commit log, mixed with manual edits, would be a great way to document the evolution of LLM assisted engineering. I wonder if there is some tool support yet that supports that.
248.
▲
by
froh
2y ago
the advantage comes with the full package, operations and all. you don't have racks with blades but one box or two, that you upgrade every few years and other than that your hardware side is covered. rewiring networks, reattaching stor
249.
▲
by
froh
2y ago
how about it being a simple gentle nod to the plain design of HN.
250.
▲
by
froh
2y ago
well, IBM very publicly invested 1Bn USD into supporting Linux on all their hardware with all their software. so db/2 on s390 on Linux, likewise websphere, etc. it gave the customers the promise of one run time environment on anythin
251.
▲
by
froh
2y ago
nope. the first enterprise Linux was SuSE on s390, then came RH on x86 and then suse there as well. but RH marketing was better back then already :-D
252.
▲
by
froh
2y ago
in a nutshell a mainframe is a cloud in a box for high throughput workloads which need crypto and tpu accelerators. mainframe pricing usually is not by pound of iron but per cpu cycle. unless you say nah I'm buying the thing, not just
253.
▲
by
froh
2y ago
oh, they'll stay around for another while. they also moved on three more CPU generations since that redbook, to z17. I think it's Linux on Z that makes it sexy and keeps it young, in addition to a number of crazy features, like a
254.
▲
by
froh
2y ago
TIL that not only the software side was chaotic (served as the backdrop of Fred Brook's "Mythical Man Month"), but also the hardware side almost failed. the article here ends around 1971 --- the mainframe would later save IBM
255.
▲
by
froh
2y ago
it may well be "cold brew", a coffee specialty that is some work to make at home and that has a very distinguished taste and contrast coffee that was brewed hot and then cooled down.
256.
▲
by
froh
2y ago
yes. and math/logics trained brains confuse hierarchical namespaces with trees. names in nested namespaces should be DAGs, maybe even arbitrary graphs, meaning a chair can be a sit-on thing in several contexts, but not in all (think
257.
▲
by
froh
2y ago
Creepy Craig is hilarious. can't be Daniel Craig because the physiology is too different. And whoever this is they're Daniel Craig's dark younger brother. https://theaiunderwriter.substack.com/p/an-imag
258.
▲
by
froh
2y ago
yes! or a 2/3 ish of the printable area column plus a 1/3 ish margin notes column. a single column on a4 simply is too wide anyhow... https://en.wikipedia.org/wiki/Column_(typography)#:~:text=Fo...
259.
▲
by
froh
2y ago
yes, XML is very mature, and fun if you have access to advanced tools. however most oss builds on libxml which is stuck in xslt 1 and xpath 2 iirc... I recently stumbled upon James Clark's youngest brainchild the ballerina language. h
260.
▲
by
froh
2y ago
usually whitespace (in) significance is specified in the XML schema. so if you provide a schema and instruct the xslt engine to comply with the schema, do your issues persist?
261.
▲
by
froh
2y ago
syntext serna was such an engineering marvel. a wysiwyg XML editor that used xslt to fo to specify your rendering. was built in the context of docbook and dita but did work for any xsd with a xslt to fo. amazing technology. ahead of its
262.
▲
by
froh
2y ago
a lisp... like dsssl ? ;-)
263.
▲
by
froh
2y ago
interrsting. I find the signal/noise ratio of XML really bad. what I really dread in XML though is that XML only has idref/id standardized, and no path references. so without tool support you can't navigate to a reference t
264.
▲
No new commits on YAML 1.3 since 2022 --- What happened?
(github.com)
1 points
by
froh
2y ago
|
1 comments
265.
▲
by
froh
2y ago
the stated goal was a major refactoring: https://www.yaml.io/spec/1-3/ the development branch (see URL) seems stalled since end of 2022.
266.
▲
by
froh
2y ago
yes! and that is composite * "a-/ad-" towards * "celeritas" speed the second derivative, of sorts: towards+speed
267.
▲
by
froh
2y ago
a nuanced point indeed. and we agree a kernel executing write_rando_stuff_to_rando_places out of the blue would be unsafe? do we also agree registers to be auch random places? then we're good
268.
▲
by
froh
2y ago
fascinating. maybe terminology issues? where I come from, the kernel must not, ever, write to unwanted locations, even if in theory it could. wrong data as you point out is a completely different point of discussion, that could be a bug in
269.
▲
by
froh
2y ago
the L4Re derivative (open source) is running in every single id.X Volkswagen car in the central "icas1" ECU, carrying Linux and other guests. https://www.kernkonzept.com/kk_events/elektrobit-advances-au... af
270.
▲
by
froh
2y ago
the point are people not using formal methods yet. automotive for example continues amazing aspire iso 26262 rain dances to tell themselves systems were safe. and does not allow to replace that with formal specs and proofs of compliance.
More ›