owlstuffing

9 ms·

91.
by owlstuffing 2y ago
Imagine v2.0 introduces a new feature that requires a parser change—one that v1.0 wouldn't be able to parse. $if $defined(C3_V2_PLUS): // new feature fn f = \ -> foo(); // this won't parse
92.
by owlstuffing 2y ago
That strategy will backfire when the grammar changes in a later release. A pre-parse step is necessary for code that targets different compiler releases.
93.
by owlstuffing 2y ago
Ah. The top-level lang description claims “No preprocessor”, but my definition of that word doesn’t appear to be the same as yours :/
94.
by owlstuffing 2y ago
Overall, this is one of the better C killers I’ve seen. But keeping macros while ditching conditional compilation? That seems completely backward to me. Oh well.
95.
by owlstuffing 2y ago
Agreed. Type providers bring metaprogramming to F# in a way that’s both powerful and innovative. The concept is amazing, enabling a new frontier for dynamically extending type safety. My only surprise is how little fanfare it has received s
96.
by owlstuffing 2y ago
You're not entirely wrong, but when it comes to SQL, the trade-offs are unavoidable. You either embrace a conventional, not-SQL approach with all its limitations, or you treat the database as the single source of truth (SSoT). Both hav
97.
by owlstuffing 2y ago
The issue is that many essential libraries and tools rely on setting internal final fields. I assume that's why the options around this have remained open-ended. The problem with these various "integrity by default" options i
98.
by owlstuffing 2y ago
CSV is everywhere. I use manifold-csv[1] it’s amazing. 1. https://github.com/manifold-systems/manifold/tree/master/man...
99.
by owlstuffing 2y ago
I use Java with manifold-units[1] for this. Some examples: ‎ > // commonly used unit abbreviations e.g., m, ft, hr, mph, etc. import static manifold.science.util.UnitConstants.*; ... Length l = 5m; // 5 meters Length
100.
by owlstuffing 2y ago
“the devil finds work for idle hands”
101.
by owlstuffing 2y ago
You mean Bengali?
102.
by owlstuffing 2y ago
I’ve been using IntelliJ’s JDBC-based UI, this will add a lot more capability. I’m using the manifold-sql[1] project with duckdb for analytics, amazing. 1. https://github.com/manifold-systems/manifold/blob/mas
103.
by owlstuffing 2y ago
>The difference between Go and Java is that in Go a type need not declare its adherence to an interface up front. Go can't declare adherence up front, and in my view that’s a problem. Most of the time, explicitly stating your inte
104.
by owlstuffing 2y ago
Most banana varieties actually taste best and last longer as they start to brown (ripen). The Cavendish—the dominant grocery store banana—is one of the few that turns mushy and unpleasant when it does.
105.
by owlstuffing 2y ago
>it comes with a huge drawback: you are limited to implementing the interfaces considered when writing the code Huge drawback? Quite the opposite. Unintentional implementation is a terrible trade for readability and type-safety, hence th
106.
by owlstuffing 2y ago
> Do you think Go is "moving up" (away from systems prog) or is Java "moving down"? I haven't been keeping score, but I've read other articles like this one claiming Go as an enterprise language alternative
107.
by owlstuffing 2y ago
>Are you aware of the trick Yes, and while it uses the compiler to ensure a type implements an interface, it's still a trick that exposes a large hole in the language... and begs for it to be filled. Most importantly, it still doesn
108.
by owlstuffing 2y ago
Going back to first principles, nominal typing is what I miss most with Go. I get the utility of structs + interfaces + structural typing, but most of the time there is more benefit in declaring that a type nominally implements an interface
109.
by owlstuffing 2y ago
> but this is the only right way of evolving a programming language when incompatible changes must be made: by providing tools that guarantee [it] Yep. I'm not a particularly big fan of Google languages, but focusing on bridging le
110.
by owlstuffing 2y ago
> I don't find it too surprising that people who are smarter make more money. Yeah, being smart definitely helps with making money, but honestly, that bar’s not as high as people think. There’s a bunch of other stuff that matters to
111.
by owlstuffing 2y ago
SSR w/ htmx is the correct answer for the vast majority of web application stories. With htmx there just isn’t any need for CSR for most apps. But another advantage of htmx is that it is incremental—you can gradually reduce CSR until y
112.
by owlstuffing 2y ago
An experimental yet comprehensive compiler plugin that brings optional parameters & named arguments to Java. Complete IDE integration available with IntelliJ.
113.
Java: Optional Parameters and Named Arguments(github.com)
2 points by owlstuffing 2y ago|1 comments
114.
Show HN: Optional parameters and named arguments for Java(github.com)
4 points by owlstuffing 2y ago|0 comments
115.
by owlstuffing 2y ago
IntelliJ CE is free and destroys any LSP in terms of dev productivity. Other than consistency, why would you not use it?
116.
by owlstuffing 2y ago
Something like manifold-sql[1] for ts would be awesome. 1. https://github.com/manifold-systems/manifold/blob/master/man...
117.
by owlstuffing 2y ago
Right, my sentiments too. I was expecting type-safe SQL . The manifold-sql[1] project has this down. 1. https://github.com/manifold-systems/manifold/blob/master/man...
118.
by owlstuffing 2y ago
Yep. They demo great, but unless your use case is on the trivial end, you either find yourself making unreasonable compromises or, if the tool provides API escapes, you’re not only coding, but hacking against the tool. In my view, mainstrea
119.
Type-Safe Data Science(github.com)
2 points by owlstuffing 2y ago|1 comments
120.
by owlstuffing 2y ago
Analytics / data science using Java + Manifold + DuckDB. Powerful, type-safe, amazing.

More ›