owlstuffing

5 ms·

31.
Optional/Named Arguments for Java(github.com)
1 points by owlstuffing 7mo ago|1 comments
32.
by owlstuffing 7mo ago
Explores advanced optional parameters & named arguments as a Java compiler plugin. Complete IDE integration available with IntelliJ. Key features - Optional parameters -- Define default values directly in methods, constructors, and reco
33.
Rethinking Syntax: Binding by Adjacency(github.com)
53 points by owlstuffing 7mo ago|23 comments
34.
by owlstuffing 7mo ago
What if these were real, type-safe expressions in Java: 2025 July 19 // → LocalDate 300M m/s // → Velocity 1 to 10 // → Range<Int> Schedule Alice Tues 3pm &#x2
35.
Type-Safe JDBC: Schema-First Native SQL in Java(github.com)
3 points by owlstuffing 7mo ago|1 comments
36.
by owlstuffing 7mo ago
This project explores schema-first, native SQL as a JDBC-enabled sublanguage in Java. The goal is to eliminate lossy intermediate subsystems (ORMs, DSLs) without sacrificing Java’s static type-safety guarantees. You write native SQL inline,
37.
by owlstuffing 7mo ago
> If somebody can get a lot done with a tool, then it's a good tool. Does "getting it done with pliers" make them a good wrench?
38.
by owlstuffing 7mo ago
Right on. Git is good at what it does, but its CLI is too low-level. It feels more like an assembly language than an end-user language, and a haphazard one at that. There are wrappers that make it much more approachable. IntelliJ’s Git fron
39.
by owlstuffing 8mo ago
Windows 3.x did not have preemptive multitasking, apps had to yield in the message loop (cooperative multitasking). This meant that an instantaneous response was possible, but often wasn't, at all. Win95 brought true preemptive multita
40.
by owlstuffing 8mo ago
Indeed! The UI in general is more intuitive compared with mod flat bs.
41.
by owlstuffing 8mo ago
Imagine a 20 person engineering team that hallucinates on a regular basis and is incapable of innovation.
42.
by owlstuffing 8mo ago
> I think we lost the plot as an industry I get your point, but generally with most enterprise-scale apps you really don’t want your transactional DB doubling as your data warehouse. The “push-based” operation should be limited to moving
43.
by owlstuffing 8mo ago
Read the docs eg. Darts: https://github.com/khalildh/garment-notation/blob/main/garme...
44.
by owlstuffing 8mo ago
Something parallel to this and completely amazing: manifold-sql[1]. 1. https://github.com/manifold-systems/manifold/blob/master/man...
45.
by owlstuffing 8mo ago
Looks like a decent start. No UDTs? Not on GitHub? AI generated?
46.
by owlstuffing 8mo ago
Yep, and... 4. the quality gap has closed considerably e.g., the function and durability of your $8k watch and a $300 watch are effectively imperceptible The gap is closing from both ends (cheap manufacturing, access to tech, etc.)
47.
by owlstuffing 8mo ago
Right... But Go is exclusively structurally typed, whereas Java with the manifold compiler plugin complements the type system's nominal foundation -- a class can still implement a structural interface nominally. Doing so enforces int
48.
by owlstuffing 9mo ago
100% agree. > Writing SQL code Language integration is paramount for med/lg projects. There's an experimental Java lang project, manifold-sql [1], that does the impossible: inline native DuckDB SQL + type-safety. "&
49.
by owlstuffing 1y ago
That is a pretty fair assessment, and I'll avoid the nominal v. structural subject, but in my experience the difference between static and dynamic typing comes down to metaprogramming. For instance, much of Python's success stems
50.
by owlstuffing 1y ago
16-bit Borland C++ is also available: https://winworldpc.com/product/borland-c/20
51.
by owlstuffing 1y ago
I agree w that, but I think Scala has deeper problems. It tries to be a better Java and a better OCaml at the same time. This split personality led to Scala’s many dialects, which made it notorious for being difficult to read and reason abo
52.
by owlstuffing 1y ago
> Aggregation is not inheritance, rather a workaround, using delegation Although the designers of COM had the right idea, they implemented delegation in just about the worst way possible. Instead of implementing true delegation with mu
53.
by owlstuffing 1y ago
Oh, how I’ve never wanted downvote power more.
54.
by owlstuffing 1y ago
Quite similar to manifold-sql[1], which is arguably better integrated into Java than SQLx is into Rust. Inline native SQL in Java is *inherently type-safe*, no mapping -- query types, query results, query parameters all projected types at c
55.
by owlstuffing 1y ago
This is yet another reason why source code sb stored in parsed AST form.
56.
by owlstuffing 1y ago
> The overviews are also wrong and difficult to get fixed. No different from Google search results.
57.
by owlstuffing 1y ago
Replace the not-TODOs with NOTEs. For example, this TODO: //todo: factor this out in case X …is a NOTE, albeit a gratuitous one. Because if X ever happens, the note won’t matter anyway, since you will have had to grok all
58.
Rethinking Syntax: Binding by Adjacency(github.com)
1 points by owlstuffing 1y ago|1 comments
59.
by owlstuffing 1y ago
What if these were real, type-safe expressions in Java: 2025 July 19 // → LocalDate 299.8M m/s // → Velocity 1 to 10 // → Range<Integer> Schedule meeting with Ali
60.
by owlstuffing 1y ago
The manifold project[1] for Java provides that feature as "Structural Interfaces" which supports polymorphic variants. The project also supports tuples that behave similarly. var person = (name: "Joe", age: 35);

More ›