mckinney

9 ms·

31.
Yes, this is Java: Length distance = 100 MPH * 3 hr;(github.com)
4 points by mckinney 6y ago|0 comments
32.
Type-Safe Unit Expressions for Java(github.com)
1 points by mckinney 6y ago|0 comments
33.
Type-Safe Unit Expressions for Java(manifold.systems)
1 points by mckinney 6y ago|0 comments
34.
by mckinney 6y ago
Ok, I get that vi is a legend etc. I think I understand why, but I'll keep that to myself. But honestly, it's a relic. Hell, it was a relic in the late 80s when I was in college! Few of my classmates bothered with it unless they H
35.
by mckinney 6y ago
Indeed, the JVM sorely lacks in the reflection/metaprogrammaing department. The Manifold framework[1] picks up where Java leaves off. For instance, @Jailbreak is a badass, type-safe alternative to reflection. [1]: https://gi
36.
by mckinney 6y ago
Reminds me of Manifold[1] for Java. But Manifold integrates seamlessly with the Java compiler as a plugin as opposed to being a separate compiler, which makes Circle less approachable imo. Still, I like the F# type provider-ish aspect of th
37.
by mckinney 7y ago
I hadn't given Odin a look before I read this post. As a fellow general purpose language author (Gosu) I applaud the author's pragmatic, albeit unpopular at times, point of view. For instance, his position regarding Null is spot
38.
by mckinney 7y ago
Can you provide an example involving "operations that relate efficiency and power factor by accident" or similar? I'd like to better understand your problem domain.
39.
by mckinney 7y ago
Java provides exceptional dimensional and unit support via the Manifold framework [1]. Length distance = 100 mph * 3 hr; Force f = 5.2 kg m/s/s; // same as 5.2 N Mass infant = 9 lb + 8.71 oz; [1] https:
40.
by mckinney 7y ago
Seldom mentioned in type system discussions like this is the notion of openness . For instance, F# is one of the very few languages addressing openness where schematic structure in data can be directly and type-safely reflected by the ty
41.
by mckinney 7y ago
The Manifold project [1] nicely illustrates the author's proposition regarding structural typing and static type systems. Using the Manifold library you can indeed create structural interfaces [2] in Java similar to those in TypeScri
42.
Type-Safe GraphQL without a code generation step or other atrocities(github.com)
4 points by mckinney 7y ago|0 comments
43.
Unit expressions with Java, remarkably expressive(github.com)
4 points by mckinney 7y ago|0 comments
44.
by mckinney 7y ago
Late to the party on this one, but I mostly agree with the OP regarding the magnitude of the evidence. Most of the comments here attempting to explain away the recent Navy reports as "experimental aircraft" are perhaps uninformed.
45.
by mckinney 7y ago
Ah the Win32 API. Oddly, I learned quite a lot of object oriented fundamentals doing C++ Win32 programming indirectly using Paul DiLascia's excellent book "Windows++"[1]. One of the few 90s era programming books I still have.
46.
by mckinney 7y ago
You confuse "Most" with "Common" e.g., A Toyota is a common car to see on the road. See.
47.
by mckinney 7y ago
As the OP points out just-in-time code generation is a huge improvement over conventional alternatives. If anything it represents a step forward considering developer productivity.
48.
by mckinney 7y ago
I never hear this idea coming up. Can you provide a reference? In any case what is the alternative? More of the same conventional code generation that destroys everyone's productivity? And is no easier to debug. In fact the just
49.
“Just-in-time code generation” the coolest language feature you never heard of(github.com)
17 points by mckinney 7y ago|5 comments
50.
Java: Operator Overloading as a Compiler Plugin(github.com)
2 points by mckinney 7y ago|0 comments
51.
Unit Expressions built into Java, seeing is believing(github.com)
3 points by mckinney 7y ago|0 comments
52.
Operator Overloading Added to Java(github.com)
1 points by mckinney 7y ago|0 comments
53.
Manifold: Java Operator Overloading, Unit Expressions, Ranges, and Science(github.com)
3 points by mckinney 7y ago|0 comments
54.
by mckinney 7y ago
Data classes are nice, but they are not a general substitution for Properties, which address the greater getter/setter boilerplate concern. That said, you can use project Lombok for that pretty straightforwardly. You can also use p
55.
by mckinney 7y ago
> This hardly sounds like a standardized feature. IDE module systems reflect the standard module system used by standard build tooling such as Maven and Gradle. > That is not true, access control is enforced both at compile time a
56.
by mckinney 7y ago
Essentially since the JPMS prohibits two modules from defining the same package (aka package splitting), you can't avoid any kind of package-related hell. So if a project depends on the Google Cloud SDK it can NOT have its own version
57.
by mckinney 7y ago
Quite a lot of shops choose not to use Scala because of the power. For instance, I can easily write Haskell-like code with Scala and build DSLs galore, which for me is great. But what happens when you need to hire more developers? That&
58.
by mckinney 7y ago
The JPMS represents what is probably the largest single change in Java's history. It significantly impacts the entire stack: language, libraries, and runtime/VM. In my experience the host of incompatibilities resulting from module
59.
Why Java Reflection is (mostly) unnecessary(manifold.systems)
4 points by mckinney 7y ago|0 comments
60.
by mckinney 7y ago
I hear you! I have vehicles with mostly touchscreen (maserati) and mostly tactile (bmw). In my view touchscreens SUCK for automotive use. But don't take my word for it. Read up on Mazda's pivot back to tactile and the research t

More ›