mckinney

12 ms·

61.
by mckinney 7y ago
Wait. Wasn't it Porsche that started all this with the Cayenne SUV? Porsche has always been near the bottom of the pedigree e.g., compared with Ferrari, Lambo, McLaren, etc., but still they are considered supercar-ish status. It&#x2
62.
by mckinney 7y ago
Ah, no relation, but interesting library!
63.
by mckinney 7y ago
Nice job! On the whole the howtographql series is instructive but results in a ton of boilerplate code. The GraphQL framework[1] from the Manifold project avoids all of that with the "manifold" concept, which is similar to F#&#x27
64.
by mckinney 7y ago
You misunderstand. It's not about the cost of the IDE but rather the cost of maintaining software and preventing defects over time. The takeaway from my comment: Toward a general policy if static analysis were built into the editor, a
65.
by mckinney 7y ago
I'm not familiar with Infer or Zoncolan, but I wonder what percentage of issues these tools detect is already covered by IntelliJ IDEA "inspections". Inspections consist of a configurable series of static analyzers each targ
66.
Manifold: Java Extension Methods and Type-Safe Metaprogramming(github.com)
4 points by mckinney 7y ago|0 comments
67.
GraphQL Perfection with Java?(github.com)
3 points by mckinney 7y ago|0 comments
68.
by mckinney 7y ago
Quote of the day: "lol the JVM does access security checking at run time, if global warming was actually a thing it would be responsible for like 50% of it and method overloading would be responsible for another 20%."
69.
Java Access Control, Stop the Insanity(medium.com)
4 points by mckinney 7y ago|1 comments
70.
by mckinney 7y ago
It's difficult to justify the macro aspect of the preprocessor, there are a thousand horror stories for every questionably good macro use-case. The only somewhat respectable macro definition usage I recall from my C++ days was type al
71.
Code Generators Are Obsolete?(github.com)
3 points by mckinney 7y ago|0 comments
72.
by mckinney 7y ago
Regardless of the reasoning laid out in the OP, it's difficult to argue in YAML's favor comparing it with JSON. I'm not an ardent fan of JSON either -- both YAML and JSON have issues wrt inconsistencies: - what draft of JSON
73.
by mckinney 7y ago
There's a short article on jaxenter covering this: https://jaxenter.com/manifold-say-goodbye-to-checked-excepti...
74.
Adios, Checked Exceptions(github.com)
2 points by mckinney 7y ago|1 comments
75.
by mckinney 7y ago
What is cool about Manifold's new preprocessor is that it does not involve extra build steps or additional file I/O as do many conventional preprocessors. Instead, via the Javac Plugin API, the preprocessor contributes as an integ
76.
Define Java_has_a_preprocessor(github.com)
2 points by mckinney 7y ago|2 comments
77.
Finally a Preprocessor for Java(github.com)
2 points by mckinney 7y ago|0 comments
78.
by mckinney 7y ago
Thanks! The 'exceptions' option is quite a bit different from SneakyThrows. The 'exceptions' option completely mutes checked exceptions in your project -- you don't have to declare a throws clause or catch a checked
79.
by mckinney 7y ago
(Hi, I'm the author of Manifold) Manifold works equally well with Java 8 - 12. While no IDE is required, it is designed to fully leverage Java's static type system, which heavily benefits from the static analysis provided by a top
80.
by mckinney 7y ago
Thank you! After I got past the initial shock with the javac codebase (it's an unusual design) I came to appreciate it. Given it's age and the number of revisions it has undergone, it holds up pretty well. But, yeah, building M
81.
by mckinney 7y ago
Note tools.jar is needed only for Java 8, and only for compile-time, unless you use Manifold's dynamic loading feature. The JREs for Java 9+ bundle what used to be called tools.jar.
82.
by mckinney 7y ago
There's a significant difference between a code gen build step and what Manifold is doing with javac. Resource files are virtual source files, this represents a leap in terms of dev productivity.
83.
by mckinney 7y ago
See my earlier comment re javac plugin API, Manifold uses that as a means to hook into the compiler. Probably the most interesting aspect of Manifold is its role as a type name resolver for the compiler. Manifold provides an API to dynamic
84.
by mckinney 7y ago
Manifold hooks into the Java compiler via the javac plugin API. This is similar to the way annotation processors work, but without the overhead of additional passes (or rounds) in the compiler. The plugin route also provides access to earl
85.
by mckinney 7y ago
It's optional. It seems scary, but checked exceptions are a feature exclusive to the Java compiler -- the JVM does not enforce them. This is how JVM languages like Kotlin and others only use unchecked exceptions, and also how Manifol