WClayFerguson

12 ms·

61.
by WClayFerguson 6y ago
I remember DCOM! I was a WIN32 MFC C++ Windows app developer from 1990 to 2000. I forget which person at MSFT finally ended up admitting "The Registry" was a mistake, but I think it was Gates? It was right around the time when WAR
62.
by WClayFerguson 6y ago
That's why experienced Java devs generally try not to put any logic code in POJOs. So you never generally even open those files unless you're expending the 5 seconds it takes to add a new prop. But as I said I could make each prop
63.
by WClayFerguson 6y ago
About 1998 when Microsoft tried to invent their own "flavor" of Java, I lost all interest in the company, and that's right when I switched from a C++ developer to Java. C# was just another "copy" of the VM concept J
64.
by WClayFerguson 6y ago
Proxy is part of JS. When did I ever say ANYTHING in JS is typesafe? Nothing in JS is typesafe. However this is also simultaneously true: You can code in TypeScript and achieve 100% type safety by putting types on everything. If I claim all
65.
by WClayFerguson 6y ago
You took the first half of my sentence pretended like that was the complete thought. It wasn't. The whole sentence is the thought. What I meant was "You can't say technology X is flawed because tools using X are flawed".
66.
by WClayFerguson 6y ago
Thanks for your two posts, I agree with pretty much all of what you're saying. When you look at the millions of man-hours that have gone into the "burn it all down and start from scratch" languages (Go, Rust, etc) and you con
67.
by WClayFerguson 6y ago
The Java languages gives you the choice of whether to use getters/setters or not. You added a good example. The main reason I love getters/setters is they are a 'hook' to add any code (like logging) if you want to detect
68.
by WClayFerguson 6y ago
I personally don't mind heated technical debates. It's unfortunate that there's so many SJW moderators hiding in their 'Safe Spaces' who think it's their job to terminate any arguments that arise. I guess they&
69.
by WClayFerguson 6y ago
I probably have 1000s of plain getters and setters in my code, and I never typed ANY of them. lol. VSCode has a "Generate Getters and Setters" refactor function, and I can make them plain publics any time I want. So you can't
70.
by WClayFerguson 6y ago
I had already given two examples of how you can create non-type-safe code in TypeScript. I mentioned 1) the 'var/let' way and 2) The "Not including types on parameters" way. You then gave an actual example of #2. lo
71.
by WClayFerguson 6y ago
Eich started work at Netscape Communications Corporation in April 1995. Eich originally joined intending to put Scheme "in the browser", but his Netscape superiors insisted that the language's syntax resemble that of Java. As
72.
by WClayFerguson 6y ago
You can write 100% perfectly type-safe code in TypeScript. You'd have to accidentally do a 'var' instead of a 'let' variable, or forget to add a type to a parameter, but if you try you can get pretty much 100% type-
73.
by WClayFerguson 6y ago
Java was perfectly dominant in it's realm only. Obviously Java is not competing in the realm of machine code generation at all, and assembly language should always exist too. C/C++ is the perfect example of a language lasting mult
74.
by WClayFerguson 6y ago
Oh, you think I'm just pushing for Java. I'm not. I'm saying having one language is better than 100. People can't share code very well if there's so many languages. Languages themselves don't need to be comple
75.
by WClayFerguson 6y ago
Exactly right. Each new language thinks they've simplified and solved problems, but in the end they end up having to solve the same old problems that have already been solved decades earlier lots of times.
76.
by WClayFerguson 6y ago
The ability share code is critical. For people to share and cooperate it's much better to have fewer languages, than 100s. Companies are spending billions each year because of having to translate from one language to another.
77.
by WClayFerguson 6y ago
That's a great point. Lisp is so simple in every way, you could make a good case that it was superior to all other languages, and that perhaps inventing Java was the mistake and Lisp should've been the "final" language.
78.
by WClayFerguson 6y ago
Here's a non-fragmented translation for ya: "The fewer languages there are the easier it is for developers to share code."
79.
by WClayFerguson 6y ago
> 200 line class which has no actual behaviour beyond boilerplate A skilled Java developer might make a huge POJO have every variable private and then implement getters and setters to control or monitor access to every member. But then s
80.
by WClayFerguson 6y ago
> I'm not sure how well you can separate that: most people are going to hit those bumps when they get started. Your XML example is spot on and I agree. However I'd never say XML itself was flawed specifically because some of th
81.
by WClayFerguson 6y ago
TS is what everyone is coding nowadays, and yes it definitely "fixed" the problems with JS. However the world would be a better place if there was just Java, and neither of it's two offspring were ever born (JS and TS).
82.
by WClayFerguson 6y ago
Q: Why does TypeScript exist? A: To fix JavaScript. Q: Why was JavaScript invented? A: To run code in the Browser. Q: Why didn't they run Java in the Browser? A: They did (applets). They tried. They failed. So they had to start over. T
83.
by WClayFerguson 6y ago
JavaScript and even modern TypeScript has syntax that is extremely similar to Java, so you can't really say that when I claim Java was already "mostly" everything we needed (WAY before "Go" and "Rust" were
84.
by WClayFerguson 6y ago
The horse-drawn carriages analogy is not applicable because I'm using Java in my current project, like most other large corporations, I don't find it antiquated, I find it "state of the art". There are some improvements
85.
by WClayFerguson 6y ago
If you don't think Java was ever dominant (and frankly I think it still is), then probably we just disagree about the definition of the word "dominant".
86.
by WClayFerguson 6y ago
I think the world was almost tolerable before Go and Rust came along. We already had too many languages even before those two, but at least there was a clear leader: Java. Nowadays the market is completely fragmented.
87.
by WClayFerguson 6y ago
Right, I think the languages that compile JVM bytecode were much more heading in a better direction than the ones who said "let's have fun and just start from scratch, and further fragment the industry"
88.
by WClayFerguson 6y ago
You're conflating the monstrosity of J2EE (which admittedly was a mess, and completely unrelated to Java itself) with the "Java Language" by which I mean the syntax of the language itself. Yes the younger/newer generatio
89.
by WClayFerguson 6y ago
Improving a dominant (but broken) language is called "innovation" and "improvement". There's no reason all your magic bells and whistles couldn't have been added into Java. Creating new languages just made life
90.
by WClayFerguson 6y ago
I don't mean Java was perfect from day one and forevermore. I mean it was the language that was perfectly dominant and acceptable at the time, and could've been extended and kept backwards-compatible, rather than restarting new la

More ›