amzans

18 ms·

211.
by amzans 8y ago
What do you mean by "warn-up much faster"? Go doesn't have a JIT compiler so not sure what you need to warm up?
212.
From Java to Go, and Back Again (2016)(opencredo.com)
117 points by amzans 8y ago|130 comments
213.
Kotlin Meets Gradle(blog.gradle.org)
1 points by amzans 8y ago|0 comments
214.
Machine Learning: The High Interest Credit Card of Technical Debt (2014)(ai.google)
576 points by amzans 8y ago|88 comments
215.
7 lines of code, 3 minutes: Implement a programming language from scratch(matt.might.net)
2 points by amzans 8y ago|0 comments
216.
Go: The State of Developer Ecosystem Survey in 2018(jetbrains.com)
3 points by amzans 8y ago|0 comments
217.
by amzans 8y ago
As a frequent Berlin-Munich traveller, it’s such a joy to now be able to make this route in less than 4 hours directly from and to the city center. Last month I had to instead take a flight (direct ~1h) but it ended up being more stressful
218.
Announcing the Build Server Protocol v1.0(scala-lang.org)
2 points by amzans 8y ago|0 comments
219.
by amzans 8y ago
Yet case classes with pattern matching and pure functions leads to some of the most readable code I’ve seen, without requiring much FP knowledge. Unlike OOP in which the logic is hidden away in some AbstractVisitorBuilderFactory and a sea o
220.
My Life as a Tech Transfer Monad by Erik Meijer(youtube.com)
2 points by amzans 8y ago|0 comments
221.
The Future of Machine Learning is Tiny(petewarden.com)
3 points by amzans 8y ago|0 comments
222.
A neural approach to relational reasoning(deepmind.com)
2 points by amzans 8y ago|0 comments
223.
Deep Dive into Spark SQL’s Catalyst Optimizer(databricks.com)
2 points by amzans 8y ago|0 comments
224.
DeepDSL: a domain specific language for deep learning(github.com)
1 points by amzans 8y ago|0 comments
225.
The future of computing(youtube.com)
4 points by amzans 8y ago|0 comments
226.
Understanding How Graal Works – A Java JIT Compiler Written in Java(chrisseaton.com)
3 points by amzans 8y ago|0 comments
227.
Realtime Data Processing at Facebook(research.fb.com)
2 points by amzans 8y ago|0 comments
228.
Under the hood: Photo Search(code.facebook.com)
1 points by amzans 8y ago|0 comments
229.
by amzans 8y ago
I understand the problem with that, and agree with you. While it can be very empowering to have a "sandbox" language, when it comes to shipping features and working in a team setting, it can require a lot of discipline to keep the
230.
by amzans 8y ago
IMO Scala has a lot of very well thought out features that complement each other, and this is only going to get better with the move towards Dotty. For me it feels not as bloated as other languages which added features without thinking abou
231.
Revisiting Scala(glennengstrand.info)
4 points by amzans 8y ago|0 comments
232.
Micro-Services: Scala vs. Clojure(glennengstrand.info)
4 points by amzans 8y ago|0 comments
233.
Idiomatic Go(dmitri.shuralyov.com)
3 points by amzans 8y ago|1 comments
234.
Structural Pattern Matching in Java(blog.higher-order.com)
3 points by amzans 8y ago|0 comments
235.
Building a Company on Scala(youtube.com)
1 points by amzans 8y ago|0 comments
236.
Identifying the DNS server used to fulfill an HTTP request (2013)(5f5.org)
10 points by amzans 8y ago|3 comments
237.
by amzans 8y ago
Edit: I had used a quote from the blog post as the title, but updated it to match the blog post as I realised it was a mistake. The original title was: "Go feels under-engineered because it only solves real problems".
238.
Thoughts on Five Years of Emerging Languages(al3x.net)
2 points by amzans 8y ago|0 comments
239.
GDPR Hall of Shame(gdprhallofshame.com)
2 points by amzans 8y ago|0 comments
240.
Throw Money at It(robnapier.net)
1 points by amzans 8y ago|0 comments

More ›