adriaanm

7 ms·

1.
by adriaanm 26d ago
I was too, so I used Claude to port Plato to my Paperwhite 3: https://github.com/adriaanm/plato It also has a cli to let you push docs over WiFi. Oh, and a HN reader. I have another repo with the user space I use, but
2.
by adriaanm 8y ago
This guy has an agenda. I would check his numbers yourself.
3.
by adriaanm 8y ago
Ditto. I just moved from the Bay Area to Lausanne for many of the same reasons (except the vacations: still working for the same awesome employer).
4.
by adriaanm 9y ago
+1 I use them in Lausanne. 777 CHF/year is a great deal! Interesting model: the price is the same for everyone, while bandwidth is the maximum they can offer in your location. Excellent support. I bought a TP-LINK MC220L + patch cables
5.
by adriaanm 9y ago
Good to hear! I agree :-) It was a necessary transition because we need to keep attracting customers that initially are reluctant to invest in Scala training. We've found our Java APIs to be a potent gateway drug to Scala, with many of
6.
by adriaanm 9y ago
> Typesafe->Lightbend transition The renaming never affected the staffing of the Scala team at Lightbend -- we've been doing about 2/3 of core Scala development (major thank you to the community for the other third!) since 2
7.
by adriaanm 9y ago
> I am reluctant in part because Scala.js does not quite have financial support of Lightbend. Or so it seems, it's a bit hard to tell where Lightbend ends and the non-profit Scala Center begins. As the Scala team lead at Lightbend,
8.
by adriaanm 10y ago
Procedure syntax (the last two lines, lacking the `=`) will be deprecated in Scala 2.13. The two variants before those are due to type inference. Are you really arguing against type inference? The empty argument list `()` is a convention to
9.
by adriaanm 10y ago
Thanks for your balanced reply. Sadly, some people see it as a badge of honor to write super clever code that's essentially write-only, and Scala somehow triggers this in them :-) We, as the Scala community, play an important role in s
10.
by adriaanm 10y ago
[Scala team lead at Lightbend here] I'm always eager to learn how we can improve Scala, especially as we kick of the Scala 2.13 cycle (hard at work on compiler performance and standard library improvements). Email is 'adriaan.at(&
11.
by adriaanm 10y ago
Thanks, glad you like it! We at Lightbend (my employer) don't think of ourselves as very corporate, but we definitely sponsor Scala development. My team is hard at work on Scala 2.13 (well, except the part of it that's commenting
12.
by adriaanm 10y ago
Which non-orthogonal and/or incoherent features do you have in mind?
13.
by adriaanm 10y ago
The only thing on your list on your blog [1] that's still true is that we care about PL research. Since 2.10, we've worked really hard on improving the migration between major versions, and the feedback has been very positive. We&
14.
by adriaanm 10y ago
With scala async, you can also express this in direct style: https://github.com/scala/async .
15.
by adriaanm 10y ago
Yep, 2.11.9 is the last planned release, but we would release another one for security fixes or anything as severe. If we get customer requests for backports, we (usually) also release those publicly. Thanks for your support!
16.
by adriaanm 10y ago
Thanks for the example. We agree that this is a tricky part in the collections. For Scala 2.13, our headline feature will be simplifying/refining the collections API. One of the areas we'd like to improve is to make the transition
17.
by adriaanm 10y ago
I see how people might look at how close java & javax are, and think scala & scalaz are equally close. They are not. Scalaz is a completely separate project from the core Scala project.
18.
by adriaanm 10y ago
As the Scala team lead at Lightbend, I'm truly saddened to see posts like this. It couldn't be farther from our intentions and interests! We absolutely want outstanding Scala documentation, and would never stand in the way of imp
19.
by adriaanm 10y ago
None of this makes any sense to me (except that these unfounded claims are not charitable). Lightbend (my employer) builds our whole platform in Scala, and we are proud to say you'll have the best experience using it from Scala (though
20.
by adriaanm 10y ago
True Scala 2.12 generates byte code that requires a Java 8 VM. Scala 2.11 will be supported for a while longer, with as many as the 2.12 features implemented there first (those that don't require Java 8).
21.
by adriaanm 10y ago
Keen eye! The release is tagged and the artifacts are indeed on maven central, but we are holding the official announcement for a few days to be able to launch with a nice set of community libraries already published. So much for flying und
22.
Understanding Trump(georgelakoff.com)
1 points by adriaanm 10y ago|0 comments
23.
by adriaanm 10y ago
In addition to being supported by the community, we (Lightbend) offer commercial support for Scala 2.11. If you're paying Oracle for Java 6 support beyond its EOL, perhaps you'd be willing to establish a commercial relationship w
24.
by adriaanm 10y ago
Yes, if you're tied to Java 6, you're also tied to Scala 2.11. Why is the former version peg ok but not the latter? We do everything we can to enable 2.11.x maintenance by the community (and contributions are trending up!), as wel
25.
by adriaanm 10y ago
The code emitted by 2.12.0-M5 is slower in certain benchmarks, but I don't expect this to be the case for the final 2.12 release. We're working on the performance issue, with help from the team at Oracle. The problem is likely the
26.
by adriaanm 10y ago
Hi, Scala team lead at Lightbend here (I left academia in 2012 to lead the team). We dropped Java 6 because we did not anticipate any business case for it, based on surveying our customers (we have continued to monitor the adoption of Java
27.
by adriaanm 10y ago
Thanks, I appreciate it! Also, thank you for sharing your feedback & concerns. I acknowledge we need to communicate more.
28.
by adriaanm 10y ago
We share your concern. As I said in my comment above -- the Scala and Dotty teams actively work together (we have our roots in the same research group at EPFL) to make sure Scala 2.x evolves towards Dotty and Dotty evolves towards Scala 2.x
29.
by adriaanm 10y ago
Wrong, there's more Scala than Java in Lagom's implementation, as is easily verified on the link you provided yourself. See my comment above on some more info on the Scala team.
30.
by adriaanm 10y ago
Without getting too philosophical, I don't see what's so ominous about the present not being the future or vice versa. All we have is the present, really. It's easy to verify for yourself who's working on Scala right now

More ›