yamalight

Primarily on my kinda-side project Exoframe [1]. We needed a self-hosted tool that allows simple one-command deployments and I've ended up building it myself using Docker. Seems to work pretty well so far :D

[1] https://github.com/exoframejs/exoframe

There are some (naive) benchmarks available for most http frameworks from fastify guys here: https://github.com/fastify/fastify#benchmarks

umatrix [1] from gorhill (ubo dev) does that pretty well (along with a bunch of other things)

[1] https://github.com/gorhill/uMatrix

Got tired of fiddling with deployment and built Exoframe [1] that handles most things during project deployments for me.

[1] https://github.com/exoframejs/exoframe

I've created a video series on advanced javascript (i.e. how to go from basics to product), people wanted more help, so I'd set up a Discord server where I help viewers with their js questions. It's a pretty cool experience since I quite frequently get question that make me go: "hmm, I have no idea how / why / where", so I have to learn more myself.

postdoc

Shameless plug: I did a free open source video series called "Building products with javascript" [1] that covers building CRUD webapp using javascript (including es6+), node, express, react, redux, rxjs and all that kind of stuff. Will be happy to answer any questions :)

[1] https://github.com/yamalight/building-products-with-js

Shameless self-promotion:

If you are interested in front-end and/or node.js courses (javascript, react, webpack, all that kind of stuff) - I've been doing a free open source course called "Building products with javascript" [1] that is aimed at intermediate/advanced developers who want to learn javascript more in-depth.

[1] https://github.com/yamalight/building-products-with-js

That is usually done for large research projects that collaborate with industry and require high quality code (e.g. EU-funded project "HOBBIT"; https://project-hobbit.eu/)

That nobody cares which language/stack/libs you use as long as it works.

Last year I've started a course on youtube about building products with javascript [1]. The initial idea was to make a free open source course for people who are already comfortable with language, but don't know how to start building things. The coolest (and unexpected) part was the questions I got from all sorts of people - they made me go into the details a whole lot more than I ever did just working on things. And, of course, all the gratitude from people is quite satisfying too :)

[1] https://www.youtube.com/playlist?list=PL_gX69xPLi-ljVdNhspjZ...

> As most people well know, all programming languages have their faults. ... However, JavaScript is especially bad.

> I’ve been writing web applications for over a decade and it’s utterly shocking how little JavaScript I know!

I've noticed that most people slamming js either have zero or very little knowledge of the language itself as well as environments it works in. Maybe, just maybe, it's worth learning a bit more about how and - more importantly - when js works.

Fair enough!

Looks like it might be a good time to move code from v4 (that had all those swallowing issues) to v7 and just forget about that. Promises sure came a long way :D

The errors won't be swallowed only in two cases: either if router.get actually supports promises (thus catches all the bubbled errors on its own) or if you have unhandledRejection global listener. Some node versions do show unhandled rejections automatically (e.g. v7.x), but that is getting deprecated soon.

So, there's quite a real risk of quiet failures in that bit of code.

Upd. Looks like even though the unhandled rejections warnings are getting deprecated, the rejections themselves will actually stop the code execution with non-zero exit code! Which means most of the issues I had with that code are gone (which is awesome)

This would quietly swallow all the errors though

I've paid for it as soon as I graduated and got a job that had decent salary. Totally worth it.

I'm currently building a React app while trying to explain how/what I do in weekly(-ish) videos. You can find the source code (along with links to videos) on github: https://github.com/yamalight/building-products-with-js

We tried to use locally installed sharelatex instead of our SVN papers repository in our research group. Good god, did we switch back really quick - not only the install process is godawful (no proper docs, outdated instruction, outdated dockerfile, missing docker-compose, took me a week to figure it out), absence of any stability along with zero way to administer it properly (no UI for users management, you have to send commands through shell to provide admin rights) just killed it for us. :\

That guy slams Star Citizen every half year or so. Occasionally he releases his own games that are promoted as "better than SC", but turn out to be absolutely abysmal [1].

I did backed SC almost at the very start. I think it progresses quite nicely. They are slow, sure. But they are extremely open about dev process (and progress) and it's actually really interesting to observe how such a large project is coming to life.

I can wait a few more years for a game that ambitious. World of Warcraft took 6 years to develop. SC is still on year 4.

[1] https://www.youtube.com/watch?v=2Lw-cwIGuy0

It's worth noting that the law is not only about messengers, it covers all "data handlers". So, include Google, Microsoft and all others in that list of companies too. Here's a nice overview of what this legislation is about: https://meduza.io/en/feature/2016/06/22/irina-yarovaya-s-ant...

Java, Go and Node depending on requirements.

uMatrix is amazing, but does takes more time to set up. It pays off though - page load times and page sizes are on average ~50% less.

I'd recommend starting with "React How To" by Pete Hunt [1] - it's one of the best collections of starter guides you'll need to get started with React.

And then you can always look at awesome-react. [2]

[1] https://github.com/petehunt/react-howto [2] https://github.com/enaqx/awesome-react

Congrats on the marriage!

During the first month we'd released a second alpha of our project that allows to build real-time data processing/visualisation pipelines in the browser. And now we're on track to allow building those pipelines using natural language input (target is to create a pipeline from someone saying, e.g. "what people on twitter think about brand X?")

I do 10 min exercise routine (mostly stretching and couple minutes of meditation) before sleep - works pretty well.

Continuing to move forward my ES6 React application generator [1] along with complementary client-side reactive message bus [2] that can be used as a Dispatcher.

[1] https://github.com/turrisjs/generator-turris [2] https://github.com/rxmqjs/rxmq.js

Both GOG and CDPR are a subsidiaries of CD Projekt. So, it's not all that surprising :) But they definitely deserve props for lots of things, not just being DRM-free.

and GOG.com that pushes no-DRM approach (which is way better than cracking groups for everyone)

why wait when you can use it today with 6to5 or traceur? obviously you'll need a build step, but if the app is larger than tiny, you probably already have one.

Do interesting projects? If it's boring, I usually don't do it (unless it's some sort of educational project I picked to learn new tech, but those tend to be pretty short)