News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by StavrosK on Wednesday October 18, 2017 @11:13AM (#15499762)
Django's ecosystem has spoilt me so much that it's very hard to switch to another language, at least as far as web apps are concerned. I would love to play with Rust/Nim more, but most of the side-projects I'm passionate about involve at least a few things that Python has a lib for that would be a huge time sink to rewrite in another language.
Re:Why we switched from Python to Go by arc776 on Thursday October 19, 2017 @07:25AM (#15506958)
Nim ameliorates this somewhat by being able to easily wrap any C/C++ libray, and even has c2nim to create wrappers automatically.

One of the advantages of compiling to C and C++.

Re:Why we switched from Python to Go by stavros on Thursday October 19, 2017 @07:32AM (#15506987)
I wonder if it's easy to get Nim to run on the ESP8266, huh.
Re:Why we switched from Python to Go by arc776 on Thursday October 19, 2017 @08:35AM (#15507318)
It appears so: https://github.com/TomCrypto/caret

> This is an experiment for running Nim code on the ESP8266 ("NodeMCU") microcontroller. The end goal is an extendable framework on which to build autonomous ESP8266 applications, along with an associated web service which acts as a base station providing back-end message aggregation and front-end information display/control panel.

Re:Why we switched from Python to Go by steveklabnik on Wednesday October 18, 2017 @12:26PM (#15500487)
What libraries are you most missing for Rust?
Re:Why we switched from Python to Go by StavrosK on Wednesday October 18, 2017 @07:42PM (#15504269)
These days I mostly do web, so Django and the whole ecosystem are just missing from Rust, but I'd settle for just the ORM. I found Diesel pretty hard to get started with, unfortunately :/

My other hobby is microcontrollers, and I would love it if I could run Rust on my ESP8266. I can already run MicroPython, but it feels a bit hacky (probably unfairly), and it would be amazing if I could use Rust and easily link in all the C/C++ libraries the Arduino framework has available.

I know this reply isn't useful (I miss all the libraries, woo), but it's as specific as I can get. I started a very simple website uptime monitoring service:

https://gitlab.com/stavros/panoptes

I didn't get very far before the difficulty of integrating Diesel just stalled the whole thing.

Re:Why we switched from Python to Go by steveklabnik on Wednesday October 18, 2017 @10:03PM (#15504942)
Yeah, Diesel is tough; they're working on better docs which should help out quite a bit.

IIRC someone is working on the ESP stuff...

> I know this reply isn't useful

Naw, it's all good: it's just as much about qualitative as quantitative. It's also because I'm writing a small framework in Rust in my spare time, so "rust for web" stuff is extremely top of mind for me. Thanks for taking the time :)

Re:Why we switched from Python to Go by StavrosK on Thursday October 19, 2017 @07:02AM (#15506889)
> they're working on better docs which should help out quite a bit.

That'd be great, because I currently can't find a niche where Rust is so much better than Python that I won't just fall back to that, impeding my Rust progress.

> IIRC someone is working on the ESP stuff...

That's what I heard too, but progress seems stalled. Hopefully, in the end, it'll be easy to run on the ESP, but the biggest problem is the ecosystem (which is also much of the reason why I don't use micropython all the time). There are so many libraries for the Arduino framework that C is hard to escape.