owlstuffing

7 ms·

61.
by owlstuffing 1y ago
I hadn't come across the "Row" polymorphism term before, but it sounds more like structural typing -- for example TypeScript, and to a lesser degree Go, have structural interfaces that provide "row polymorphic" prog
62.
by owlstuffing 1y ago
Yep. Using DuckDB against conventional data sources such as JSON and CSV or even Parquet has amazing potential. Paired with manifold[1]--a Java library that makes it all type safe--and it's a game changer. 1. https://github.
63.
by owlstuffing 1y ago
The Roman Empire lasted about two to three centuries in its unified form before it began to seriously fragment.
64.
by owlstuffing 1y ago
Indeed, high trust requires more than homogeneity.
65.
by owlstuffing 1y ago
Because history treats them as a package deal. Tokugawa Japan saw foreign faces as existential threats. The Ottomans built trust only within ethnic/religious silos (millets). Rome demanded a trinity of assimilation: Latin language, Ro
66.
by owlstuffing 1y ago
True, but there’s a key difference -- those earlier waves, despite being seen as "outsiders" at the time, still came from the same civilizational foundation. Europeans, whether Irish, Italains, Germans, or Poles, shared a common h
67.
by owlstuffing 1y ago
Societal trust levels tend to correlate with cultural and racial homogeneity. The erosion of trust within Western civilization reflects this trend, particularly in the United States following the Immigration and Nationality Act of 1965 (Har
68.
by owlstuffing 1y ago
Reminds me of a book, Mailing May[1], I read to my daughter and now my granddaughter. A true story of a family on a budget who sent their daughter to see grandma as mail cargo on a train. Cute story. https://www.amazon.com/M
69.
by owlstuffing 1y ago
But in this case the passes are manual!
70.
by owlstuffing 1y ago
I didn't say there aren't acceptable reasons to reach for the print statement, there are. But for the vast majority of codebases out there, if good debugger tooling is available, it's a crime not to use it as a primary diag
71.
by owlstuffing 1y ago
Their comment conflates debugging with logging. Professional debuggers such as the one in IntelliJ IDEA are invaluable regardless of one's familiarity with a given codebase, to say otherwise is utter ignorance. Outside of logging, unle
72.
Show HN: Toward Nirvana with Optional Parameters(github.com)
1 points by owlstuffing 1y ago|0 comments
73.
by owlstuffing 1y ago
While this modification may contribute to layoffs, the general declining economy is the real culprit — the layoffs started long before the tax code change.
74.
by owlstuffing 1y ago
Well… React apps are a category of huge blobs of who-knows-what-but-it-works code. In fact, I would be surprised if AI were to generate code as rube-goldbergery as React would have you write. Shrug.
75.
by owlstuffing 1y ago
Or, if you are an AI: “I prefer the em dash — it’s my calling card.”
76.
by owlstuffing 1y ago
Nice! I’m currently using manifold-sql with duckdb for this.
77.
by owlstuffing 1y ago
Languages should strive to type safely inline SQL and other structured data. With Java the manifold project achieves this via compiler plugin. The manifold-sql[1] module provides inline, type safe, native SQL. 1. https://github.
78.
by owlstuffing 1y ago
If this interests you, I highly recommend Luca Boasso’s oberonc project for the JVM[1]. 1. https://github.com/lboasso/oberonc
79.
by owlstuffing 1y ago
Right. Oracle should reconsider the naming here: stable -> lazy
80.
by owlstuffing 1y ago
Downhill fast since JB hastily exited its offices in St. Petersburg and Novosibirsk. It’s no coincidence.
81.
by owlstuffing 1y ago
Cool tool, even cooler when paired with the manifold project for SQL[1], which has fantastic support for type-safe, native DuckDB syntax. 1. https://github.com/manifold-systems/manifold/blob/master/man...
82.
by owlstuffing 1y ago
Agree 1000% There’s a Java compiler plugin[1] that muscles in operator overloading pretty comprehensively, and works with all LTS JDKs. 1. https://github.com/manifold-systems/manifold/tree/master/man...
83.
by owlstuffing 1y ago
I suppose so, since your use of “we” includes both America and China et al.
84.
by owlstuffing 1y ago
> We never stopped manufacturing, we just stopped employing people. That’s a misleading oversimplification. While it’s true we haven’t stopped manufacturing, we did offshore a massive portion of it--especially after the Open Door Policy
85.
by owlstuffing 1y ago
Outside of government, this shift also coincides with the decline of pensions and the rise of the 401k. Career growth has always been a shared responsibility between employees and employers. In white-collar fields--especially medicine and e
86.
by owlstuffing 1y ago
Skimmed, nice writing style, on reading list. Finishing Ch. 22 before I put this down.
87.
by owlstuffing 1y ago
> No types barking No thanks
88.
by owlstuffing 1y ago
And. . . Java does not have conditional compilation.
89.
by owlstuffing 2y ago
Well, if your language gains traction that plan may not succeed. For your sake, I hope that's the case :)
90.
by owlstuffing 2y ago
You do, that's the point here. You need ifdefs in this example to selectively compile the same code with different compilers, or different language levels with the same compiler. In either case C3 will fail while parsing a newer featur

More ›