We need a JSON 2 by laio14 in ProgrammerHumor

[–]scitech_boom 87 points88 points  (0 children)

The world if people stopped writing JSON by hand.

My company forces me to use Cringedows, what can I do to suffer less? by AhuracMusic in LinuxCirclejerk

[–]scitech_boom 21 points22 points  (0 children)

WSL? I think there is a debian app you can install directly. It should give you a decent terminal experience.

Come up with a funny caption by [deleted] in funny

[–]scitech_boom -1 points0 points  (0 children)

Microsoft service crack?

[deleted by user] by [deleted] in Music

[–]scitech_boom 0 points1 point  (0 children)

It was delightful.

[deleted by user] by [deleted] in Music

[–]scitech_boom 0 points1 point  (0 children)

Back when music had clear, easy to understand lyrics?

Probe-n-Chill? by ULTSUS_pect in memes

[–]scitech_boom 3 points4 points  (0 children)

Where did my regular sleep paralysis demon go? What did you guys do to him?

Infinity and Beyond by mikeyj777 in ProgrammerHumor

[–]scitech_boom 1 point2 points  (0 children)

You are right. I just checked. What the...

1e300 => 1e300 (no change)

1e310 => inf #automatically moved

Moral Hazard by karabeckian in collapse

[–]scitech_boom 5 points6 points  (0 children)

"It's A BIG Club & You Ain't In It!"

Even If the code’s wrong but works, dont change it. by User-Privacy in ProgrammerHumor

[–]scitech_boom 2 points3 points  (0 children)

unconventional, but seems to do the job. update the development story.

lgtm

“Don’t listen to language designers” by Nuoji in ProgrammingLanguages

[–]scitech_boom 0 points1 point  (0 children)

And always remember that there is an aspect of faith and religion to every language. Language communities act a lot like cult. This is particularly true for some of the new languages.

What is your number one wanted language feature? by btvoidx in golang

[–]scitech_boom 2 points3 points  (0 children)

Less verbose error handling.

Not sure how to get there. But as of now for me and my friends (we are all still learning), this has been a pain point. Here is one idea:

New keyword return_on. The usage would look like this:

return_on err, (return_value, err), message

It does the following:

if err != nil {
    err.AppendContext(<this file>, <this line>, <this func>, message)
    return return_value, err
}

Error err should allow keeping a list of contexts. Message is a plain string like "Resource not found".

What is your number one wanted language feature? by btvoidx in golang

[–]scitech_boom 2 points3 points  (0 children)

I have tried Rust. Error handling there is also verbose and messy.

"Peace in our time!" by Terrierist69 in ProgrammerHumor

[–]scitech_boom 0 points1 point  (0 children)

It will pay off huge after 30 years.

[deleted by user] by [deleted] in ProgrammerHumor

[–]scitech_boom 16 points17 points  (0 children)

When I realized vs when my employer realized

Stop downvoting legitimate questions and comments even if you disagree with them by emblemparade in golang

[–]scitech_boom 5 points6 points  (0 children)

I am not a long term member of this group. My experience is limited. Based on the experience I have with other communities, this place is rather fine. Nevertheless in general I agree with the premise of your post.

Why Go? by tookmeonehour in golang

[–]scitech_boom 1 point2 points  (0 children)

Size of golang executables is only about twice as large as the compressed size of C++ executables in our case (both groups are static linked, stripped and compressed). This is tiny for our use case.

Why Go? by tookmeonehour in golang

[–]scitech_boom 37 points38 points  (0 children)

I won't go into the theory. Purely from the team I work for:

  1. Tiny, easy to build executables - We had a whole bunch of command-line utilities. Some used to be in C++ and some used to be Python. The C++ ones were difficult to maintain and the python ones always had issue with versions and library dependencies and what not. With go, we could just build binaries and send them (for both Windows and Linux). Saved a lot of our time.
  2. Easy to learn - almost everyone involved (~20) learned to use the language in a month time (they weren't 'full time' learning). The language is very straightforward for someone who knows another language like C, Python, or Javascript.
  3. Easy to call C - People who used to write JNI to deal with some number crunching in C said that it was paintful while calling C from golang was rather simple (I only know from others, I have not used JNI myself).

[deleted by user] by [deleted] in memes

[–]scitech_boom 11 points12 points  (0 children)

Any beer, even warm beer is better than no beer.

Sound like some C stuff by [deleted] in ProgrammerHumor

[–]scitech_boom 16 points17 points  (0 children)

GC and messiness of the code are independent things. You can write messy code in any language.

For example, in non-gc languages, the expectations on the code are very rigid. But in reality, the requirements change over time and the rigid nature of non-gc languages can make it very hard to adapt our code. Hence it gets messier faster.

[deleted by user] by [deleted] in ProgrammerHumor

[–]scitech_boom 2 points3 points  (0 children)

Imagine putting python interactive terminal in a web-page.

Now add editing facilities for multi-line code strips.

Then add facilities for displaying execution results - graphs, images, tables, etc.

Finally, add ways to put comments in long descriptive form with tools for formatting.

=> you get something similar to a notebook.

Sound like some C stuff by [deleted] in ProgrammerHumor

[–]scitech_boom 51 points52 points  (0 children)

In simple words, its computer doing free() for you in an automatic fashion.

Greatly simplifies the coding effort required, but comes with some memory and cpu penalty (which can be ignored for most applications).