Rotareti

15 ms·

91.
by Rotareti 8y ago
It doesn't make BEAM pointless, but fault-tolerance and scalability (two of the core features of Elixir/BEAM) are also handled by k8s. If you use Elixir/BEAM for these features and deploy on k8s, it may seem redundant to
92.
by Rotareti 8y ago
ReasonReact for the Frontend. Python/Sanic for the API. PostgreSQL for the database. Kubernestes on DigitalOcean (or similar kaas provider) for hosting.
93.
by Rotareti 8y ago
> Is it a problem with all raspis? My Pi currently has an uptime of 388 days. I use it as a file-server/backup-machine in my home network. It runs hourly backups for multiple boxes in the background (I use vhpi [0] for this). I have
94.
by Rotareti 8y ago
Two words: typing, mypy [1] The editor support that I get from typing/mypy is fantastic! It feels like writing in a statically typed language. To me this is by far the most important feature of Python3. It's a godsend for larger&#
95.
by Rotareti 8y ago
I've been using mypy for a while now and I love it! I added mypy type annotations to a bunch of old projects and it found some bugs no one was aware of right away. I love the support I get from mypy within the editor. It works flawless
96.
by Rotareti 8y ago
That's the reason I choose OSS for everything where the data is important to me.
97.
by Rotareti 8y ago
I use yapf and in such cases backslashes work fine: x[1][4] =\ a[2] + b[4]
98.
by Rotareti 8y ago
https://edgedb.com/
99.
by Rotareti 8y ago
> Typing in python is weird, i much prefer flow/typescript. I find the exprience working with TypeScript and Python/Mypy very similiar. (in VSCode) > Async in python has a history of being weird, from twisted, to yield fr
100.
by Rotareti 8y ago
If you need UPS you can put a simple USB battery between the charger and your Pi. Works like a charm. My Pi has been making hourly backups of 3 machines in my home network without a single reboot/intervention for 347 days.
101.
by Rotareti 8y ago
My equivalent of this is insects. My family and I made a lot of trips with our car in the 90th. The front of the car was full of squashed insects when we arrived. There was a constant knocking on the windshield. The amount of insects that I
102.
by Rotareti 8y ago
> I hate working in white space sensitive languages. I think it's funny how people still have issues with this in 2018.
103.
by Rotareti 8y ago
If you find yourself using ImmutableJS, Ramda, Recompose, etc. in your React project, you should have a look at ReasonReact. It felt like a breath of fresh air to me.
104.
by Rotareti 8y ago
There is another interesting approach on the horizon: https://github.com/Nuitka/Nuitka Nuitka compiles your Python code to C and leaves you with a single file binary. It also improves performance.
105.
by Rotareti 8y ago
Me too. There is a library that solves this: https://github.com/Infinidat/munch from munch import Munch foo = {'a':1, 'b':2} foo = Munch(foo) print(foo.a) # 1 print(foo[&#x2
106.
by Rotareti 8y ago
Nuitka is awesome. I used it to compile a Python command line tool recently and it worked fine. In fact, it worked so well that I added a Nuitka build script to that project... But Nuitka is written and maintained by a single person [0]. I
107.
by Rotareti 8y ago
> try to maintain > 10k LOC codebases in Python to understand what I mean. Since Python 3.5 you can use type annotations: def my_func(foo: str, bar: User) -> None: baz: int = User.qux This is a useful feature fo
108.
by Rotareti 8y ago
> I couldn't think of any other way to do it that wouldn't result in some downtime if I had to change or upgrade packages. https://github.com/helm/helm ? You push the new version of your app as a helm ch
109.
by Rotareti 8y ago
> thanks for the details, and sorry for the perhaps distracting question: how do you handle DNS for the servers on your foo.com? No worries :) I use digitalocean for the nodes, storage volumes, etc. and namecheap to register the domain
110.
by Rotareti 8y ago
I migrated all of my services to k8s in the last ~6 months. The biggest hurdle was the development environment (testing and deployment pipelines). I ended up with a homebrewn strategy which happens to work really well. # Local development &
111.
by Rotareti 8y ago
I hope some day some big corp decides to write a decent (open source) Python to C compiler, which makes optional optimizations based on type annotations. I find this project: https://github.com/Nuitka/Nuitka very inte
112.
by Rotareti 8y ago
I just finished a ReasonReact project which I started about 3 month ago and I found the experience quite nice (working with VSCode). ReasonML is still in an early stage, but I prefer it over JS/TS for React frontends. The language is a
113.
by Rotareti 8y ago
> which has a python implementation I think this is the most popular one: https://github.com/ReactiveX/RxPY This one is a rewrite of RxPY, that makes use of async / await / asyncio: https://gi
114.
by Rotareti 8y ago
I hope some of the (new?) concepts from trio find their way into the standard lib. trio: https://github.com/python-trio/trio trio compared to asyncio, goroutines, etc.: https://stackoverflow.com/a/
115.
by Rotareti 8y ago
Does anyone know how well Python and Rust team up compared to Python and C in practice?
116.
by Rotareti 8y ago
> Not that person, but what put me off arch is that they aim to provide "vanilla" packages, which means I have to configure everything on my own. I highly suggest Antergos [0]. It's a pre-configured, easy to install Arch L
117.
Reason 3.3.2 released(reasonml.github.io)
3 points by Rotareti 8y ago|0 comments
118.
by Rotareti 8y ago
The last ReactJS project I was working on ended up with libraries such as Ramda , ImmubtableJS , recompose , etc, in order to make the codebase more functional ... We also switched to TypeScript for the type-system. While these libs imp
119.
by Rotareti 8y ago
You could create an issue template that explains the rules. If people still file support issues, you close those with a friendly reminder text (copy/paste) in which you explain the reasons why this is not the place for support. If pe
120.
by Rotareti 8y ago
Why not just close the issue and direct the person to stackoverflow, superuser, etc. if you think it falls into that category?

More ›