airless_bar

7 ms·

1.
by airless_bar 10y ago
Just read my other reply.
2.
by airless_bar 10y ago
Wrong.
3.
by airless_bar 10y ago
You are obviously wrong. While attacking a single package would be possible, covering any interesting amount of "typo"-space would require registering huge amounts of namespaces. If package manager developers are smart, the alloca
4.
by airless_bar 10y ago
Scala! Great language, huge ecosystem, good tooling, many platforms supported.
5.
by airless_bar 10y ago
This only seems to be an issue for languages where packages reside in a global namespace, like Python, Rust etc. I think most languages these days are a bit smarter and avoid this beginner mistake (for various reasons).
6.
by airless_bar 10y ago
I don't think anyone considers Python or Java modern. Nevertheless, this isn't about where adoption comes from, it's about how the language design was influenced by the advancements in language design in the last 40 years.
7.
by airless_bar 10y ago
I think dismissing anything invented after 1960/not invented at Google counts as "inflexible and unadaptable; unable to keep up with new languages or idioms".
8.
by airless_bar 10y ago
Hey, they are Google! Java 6 is probably the most "modern" thing they can think of!
9.
by airless_bar 10y ago
Costly: yes. Why not use another language? I think it's a perfectly valid question for that guy to ask. My personal opinion on "Why not use another language" is a bit different though: Adopting a different language might make
10.
by airless_bar 10y ago
I don't believe that the question was meant to be a joke or a trolling attempt. The guy's competence isn't the issue. It's the requirements of what the fix can and cannot do. _Everything_ is a mess due to the massive tec
11.
by airless_bar 10y ago
To save him time and frustration due to his project going nowhere?
12.
by airless_bar 10y ago
I think it's a very valid question. Given that the constraints by the Python BDFL rule out any reasonable solution, why not move on?
13.
by airless_bar 10y ago
> For example, you have both an option types and `null`, and libraries being inconsistent in which they pick. Which ones?
14.
by airless_bar 10y ago
Yes, Scala is great. Way ahead in terms of providing developers with useful tools compared to most other languages. (It's not the usual run-of-the-mill language which takes Java and adds some syntactic sugar, so some effort in learning
15.
by airless_bar 10y ago
Comes off as a bit "me too" from my perspective. In the whole list of things there is literally only a single thing which isn't already shipping/existing in Scala.
16.
by airless_bar 10y ago
I agree with lmm. The only thing where Kotlin wins is in marketing and hype.
17.
by airless_bar 10y ago
No?
18.
by airless_bar 10y ago
> I think the idea that API's (or implementations as you said) can be copyrighted is completely insane and I can't believe any software engineer would be okay with it. Which makes me think you're not a software engineer, a
19.
by airless_bar 10y ago
> Missing values are not errors. Call it whatever you want. ? only covers a small subset of interesting "conditions" while tremendously hurting "conditions" which could be handled in a better way. > Uh copyright wh
20.
by airless_bar 10y ago
Sorry, was meant to be a light-hearted response.
21.
by airless_bar 10y ago
The whole point of this was to show that Scala's types preserve the structure of the computation. It might not be very interesting in the Option[Option[String]] case but imagine Try[Either[String, Int]] or List[Future[Double]]. It&#x27
22.
by airless_bar 10y ago
Yeah, it's just that-if you look at every language ever designed-if the language ships with a built-in construct developers will use and abuse it on every occasion, and every other approach lingers in obscurity. > Which is expected
23.
by airless_bar 10y ago
Not really. The main strength of the first approach is that Option is only one type out of many error-handling structures. Not every error is handled appropriately by Option/?. If you have a language like Kotlin where they hard-coded o
24.
by airless_bar 10y ago
> formal name non-shitty > a trend in newer languages yes, only discovered a few decades ago :-D
25.
by airless_bar 10y ago
They preserve the structure of the computation.
26.
by airless_bar 10y ago
Option[Option[String]] != String??
27.
by airless_bar 10y ago
I can recommend Scala. The libraries are top-notch and unlikely to be found in other languages due to the superior typesystem. It has broad tooling support, and Scala's JavaScript backend is stable, mature and actually works (unlike so
28.
by airless_bar 10y ago
Standard Googler behavior. :-)
29.
by airless_bar 10y ago
Ah alright. yes, I think it makes more sense to define the GUI with code. Typed resources help with it. sbt-android-gradle has full support for Gradle projects, but to be honest: Gradle is utter shit. Just use the SBT plugin. it works so mu
30.
by airless_bar 10y ago
Which GUI tools do you have in mind?

More ›