Check out ionos.de. it's pretty cheap. Like 1 Euro for 1gb and 1 core
HN user
susi22
Email: anonymousmd55 at gmail
How does this differ from cooperative multi tasking?
Semantic Kernel is something like that
I'm a Clojure dev so I really like fast edit-compile cycles. Note, Ansible will happily take in JSON, so you can take your favorite language and write all the playbooks in that language. Just generate the playbooks on the fly (ie. genearte JSON not yaml) and shell out to ansible to run it. So you have all the features of ansible available but can arbitrarily build up your playbooks in your favorite language.
It's hacky code, but that's exactly what I did in Clojure: https://gist.github.com/rauhs/a72cfbeef4c80f9a58480484c49e7a...
With a normal REPL this works well especially when developing plays.
Yes! It's really good.
Try "Tac" for a new/spiced-up version of the game. It's really fun.
If performance matters a manual for loop will be faster. `arr.map()` isn't all that fast (except in the recent Firefoxes).
Spaced repetition is the most efficient way to learn associations. Thought, it's still barely.
I'm a big fan of spaced repetition. From a mathematical standpoint it's also a very interesting question: You have your forgetting curve and which gives you the probability that you still remember the association. I think there is still some rooms for improvements around there. For instance, I'm not sure if the big plays in the area adjust the forgetting curve for each individual user after they have enough data points.
Shameless plug: I actually just developed a new spaced repetition platform the last few years. I'm not official launched but it's online and works. If anybody is interested in taking part of the beta testing, email is in my profile.
229 dead from an overheated entertainment system: https://en.wikipedia.org/wiki/Swissair_Flight_111
Very much so, a very good read:
http://www.candlepowerforums.com/vb/showthread.php?141137-In...
And also: http://budgetlightforum.com/node/45314
This one is better: http://www.thrunite.com/thrunite-c2-3400-mah-compact-portabl... I asked for old laptop batteries from my relatives/friends, so I have currently around 30 of them. I also use it a lot for my bike light and hiking light.
I bought the latest version of the C2 and it charges perfectly.
There is also an implementation here:
https://github.com/rauhs/fast-weighted-median
In addition to a faster algorithm.
svc is very very common in Solaris based OSes.
That's some coincidence. I'm from about 20 min south of there (Im.). I was surprised to see KE on there.
They used to have Lisp & Clojure. No idea why it's been removed. Some is still accessible:
It doesn't. It's shown in the video.
No clue. It's not officially announced yet. He's just mentioned it on the mailing list.
That's why I'm pretty excited about what agentzh bring to the table with the commercialization (just a few weeks old) of OpenResty Inc.
Most of these faculty members do not have the resources or the ability to publish in "real" journals
I definitely wouldn't use "Most" here. The vast majority of faculty will publish in respected journals. Unless you can cite a source for your claim?
I remember back in the day, Google Closure was so advanced they even tried out shuffling code around in the final JS file and measured which way produced the best GZIP compression. They since abandoned that code though, but that's something they did over 5 years ago.
Both. CLJS is actually super fast, even on mobile (I test on lower power devices such as MOTO G4). The SPA is also pretty small if you keep dependencies out so it loads ~2-3s on a phone. That's with a large SPA with about 100+ React components.
Stack:
- It's CLJS with Datascript (huge DB), Rum and nothing else. That way I keep my js-file small (currently 170kb gzip'ed).
- Server side it's Pedestal, Cassandra, Datomic.
The tooling has always been leiningen and that's stayed consistent. Libraries are still the same on the client side. cljs.core + closure library gives you 90% of what you'd ever need. I don't use a single NPM library (Except React). I don't follow the latest fads in js-land anymore. IMO it's an ideal stack that is fast, small, stable and has much more features than anything in JS world. I don't need the latest and greatest transpiler (ES6, 8, 1000 or whatnot) since I can just use a macro that does this for me. Figwheel is incredible and should warrant anybody in the JS world to consider switching just for that... Productivity is amazing.
If you want a stable tech stack that'll stay the same for the new few years then check out Clojure + Clojurescipt. I'm still doing the same since I started a few years ago.
Regarding FE dev: I also have a technical Background (EE) and I hated any CSS (HTML isn't so bad). Though, flexbox is a life changer. It's actually enjoyable and I can get stuff done without spending hours on simple layout issues.
I'm one of those who think the JVM is a big plus instead of a big minus. For example, here is a post how you can easily deep dive into the internals of the JVM to figure out a problem: https://8thlight.com/blog/colin-jones/2017/03/17/everybody-o...
I wanna see this kind of tooling for other languages. The JVM gives you amazing tools that are already there for you even if you're not an expert.
FYI: Redis now has a module that does rate limiting for you: https://github.com/brandur/redis-cell
I used parinfer for a 1-2 months. Then I quit and switched back. Wayyyy too many silent errors that get introduced and you don't notice them until runtime. Especially if you edit code that other people wrote.
I've also seen at least 4 people in the chats/forums that had errors because of parinfer. So no, I won't recommend it to a beginner.
I've been doing Clojure full time for a few years. Here a recommendation on editor setup if you're new to the parentheses:
1. Setup Cursive ( https://cursive-ide.com/ ) 2. Start a REPL on the command line with `lein repl :start :port 38123` and connect to that repl with cursive, a remote REPL. 3. Bind and learn the following structural editing commands:
a) Grow selection (this will be by FAR the most used in the beginning)
b) Slurp.
c) Send top form to REPL.
d) Join lines
Don't ever select by line, only use "grow selection". Don't ever break any parens ("[({") imbalance. Shouldn't happend if you use "grow selection".
Editing like this will get you pretty darn productive. I used it for probably 6-7 months before I introduced more structural editing commands (Next in line is IMO "Move Forward").
The beautiful German language: To "earn" and "deserve" are the same word. So you're technically not lying if they ask "Wieviel verdienen Sie?"
That won't get you a PhD though. All PhD programs usually require original research. And the PhD students are usually the ones doing those experiments.
Silly question: Are you German? Do you have an academic degree? I ask because then you have some options for a state sponsored fellowship.