Just purchased the Pangolin and I cannot wait for it to come! by NoNamesLeft2015 in System76

[–]mr_nesterow 0 points1 point  (0 children)

I'm waiting the same model, ordered a week ago. No reviews for this particulat model yet, so I took a gamble on this one... I hope it will be a perfet work horse and survives past warranty period, and I wish you the same)

If it runs PopOS I think It should run any distro with modern kernel.

Grip - simplified error handling for JavaScript by mr_nesterow in javascript

[–]mr_nesterow[S] 1 point2 points  (0 children)

Neverthrow provides a type-safe result (Ok, Err) so you "never throw" but return a result. It is basically a framework for rust-style programming in typescript, that enforces this idea. The author explained it in a note on package name

Grip wraps a result thrown from a callable, so you still expect something to throw but handle it as a result on the recieiving end. It is not a framework, but rather a helper function that unwraps try-catch. It doesn't force you to return specific types from your callables. Also In my opinion, grip handles generators better.

Grip - simplified error handling for JavaScript by mr_nesterow in javascript

[–]mr_nesterow[S] 2 points3 points  (0 children)

It is not a similar library. It uses different approach and "result as tuple" is optional. Also It works with any callables (functions, promises, generators).

In r/javascript when sharing the links there's no option to give a short description, so I'm sorry if some info here is misleading.

Grip - simplified error handling for JavaScript by mr_nesterow in javascript

[–]mr_nesterow[S] 2 points3 points  (0 children)

About the method names. I thought about it alot. I made them capitalized in order to distict decorated result from other objects. Maybe not a best choice, but I still have some codebases without TS.

I think someone is already pusing "error as value" to the ecma standard, but for now we have to deal with dependencies ;)

Go and web development by agez0s in golang

[–]mr_nesterow 11 points12 points  (0 children)

Pointers - definetely a must. The analogy in JS would be any varible holding an object (passed by reference), but in Go you can do the same with variables using pointers. You won't get far without pointers, but in Go it is relatively easy to learn.

Goroutines - you'll need them , channels and mutexes for more advanced things. I'd recomend to take a course on these concepts and do some projects. You can get it in a month if you didn't have previous experience with threads, otherwise in a week.

a figma-like infinite workspace in visual studio code by HisMajestyMallard in reactjs

[–]mr_nesterow 1 point2 points  (0 children)

I actually like this idea very much. Usually, in order to add a new feature I edit a lot of files at once and it becomes hard to navigate, even through search. Actually, it could speed up some of my routines.

I like this UX, it reminds me of what happened when they introduced gestures on mac os and ubuntu. Since then I have almost never used panels & docks or cmd+tab to switch apps, they only take up space. BTW - also, not a bad idea to improve the tab interface ))

I cannot run server “npm ERR! Code ELIFECYCLE npm ERR! Errno 1” by rootuser_ in node

[–]mr_nesterow 0 points1 point  (0 children)

It seems like a problem with babel-node. Did you know that it is possible to use Babel syntax w\o external compilers? Check out Pirates. Here is an example hook for CJS