|
raddevus wrote: I’m terrible about memorizing things. Let the internet remember for me.
“Never memorize something that you can look up.”
― Albert Einstein
I have bad memory for some things too... I have always used this quote everytime that I forgot a formula or something like that.  
The "kiss my ass" variation when someone was trying to piss me off was:
I prefer to use my brain understanding things, because I can always look up what I forget. In your case is more difficult 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Another relevant one : "Quote: It is better to understand something than to memorize something. - Neil Degrasse Tyson
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Nice...
I didn't know about that one. It was exactly my point
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Not memorizing the drwxrwxrwx mask is like not memorizing the syntax of a while loop: yes you can always look it up, but is it worth to look every time that you have to write a while?
Besides, the syntax
chmod a + x
All add eXecution
o - w
Others Remove Write
is easier than remembering even the drwxrwxrwx mask since they are pretty simple declarations of intent.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
Quote: I’m terrible about memorizing things
When I (for some reason) did a Law degree, one of the first things they taught us was not to memorize things but to learn how to look them up when needed. Which was fine except the exams required us to memorize things! 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
� Forogar � wrote: they taught us was not to memorize things but to learn how to look them up when needed. Which was fine except the exams required us to memorize things!
That's Academia for you: Paradoxical Situations. 
Do as your told, not as you think, but make sure you think for yourself. 
|
|
|
|
|
|
PIEBALDconsult wrote: Will it do .net ?
I'm not sure. I don't think so, but there is IronPython[^] so...
|
|
|
|
|
I have never understood how you can program anything by placing white and black stones on a board...
|
|
|
|
|
Rage wrote: I have never understood how you can program anything by placing white and black stones on a board...
Yes, it is a challenge, but it's all binary, I guess.
|
|
|
|
|
raddevus wrote: makes it very easy to build to a native Exe --
And also very, very, very easy to cross-compile native EXEs. Want to compile for Windows as well as Linux? Here you go:
GOOS=windows GOARCH=amd64 go build hello.go
Or a Raspberry Pi?
GOOS=linux GOARCH=arm go build hello.go
Having said that... I'm not so keen on Go. Mainly because of:
- Error handling. I just don't like the way they do it, with a pair of error/return value. I prefer the Rust way, having a tagged union that is either error code or return value.
- Type system. Not just a lack of generics - I like the flexibility that sum types give you.
This article also resonates with me...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Yeah, the ease of building native exe is amazing.
Stuart Dootson wrote: I'm not so keen on Go. Mainly because of
Those are the main complaints I've heard elsewhere also. I wonder if it has quashed the interest in Go and if the language is already waning?
|
|
|
|
|
Quote: This article also resonates with me...
That article is a really unfair comparison designed specifically to make Rust look good. It is a large bit of Rust hype that is mostly garbage.
1. The author complains about how changing permission bits in Go under Windows doesn't change anything on the NTFS filesystem, but then praises Rust for not being able to do it at all on *any* system.
2. The author complains that Go doesn't handle invalid filenames with broken UTF8, and praises Rust for handling that, except that Rust doesn't handle that on Windows anyway.
TLDR: When Go handles failures on Windows gracefully by doing the only sensible thing, the author complains that it is broken and praises the Rust way of doing it (breaking completely).
When Rust breaks down on Windows the author praises Rust for doing something halfway sensible, and complains that Go should match the Rust bug.
The article is not one of a fair comparison. A fair comparison would be performing each tested feature on both mentioned OSes and tabulating the result, NOT doing different "tests" for each language so that your preferred language looks better.
|
|
|
|
|
No - the author is highlighting how he feels Go's design is slapdash and thrown together. Go presumes that all systems have Unix permissions - they don't. Rust presents portable functionality (is the file readonly?) in the common module, then also has a Unix specific module for full permissions.
I think it's highlighting a difference between attitudes - you say that Go "handles failures on Windows gracefully on Windows by doing the only sensible thing", whereas Rust "breaks completely". I, on the other hand, would see the only sensible thing as highlighting an error condition that needs to be handled, probably at a higher level of abstraction in the program.
I've written substantial programs in both Go and Rust. I have less confidence that the programs written in Go will handle unexpected situations gracefully.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Quote: I, on the other hand, would see the only sensible thing as highlighting an error condition that needs to be handled, probably at a higher level of abstraction in the program.
If that was at all a sensible choice, then WSL would have been stillborn. If that was a sensible way to go then git-bash wouldn't work on Windows.
Things that chose your "sensible" handling just wouldn't work. Things that didn't choose that "sensible" method work fine (git, WSL, cygwin, everything else that gets ported to Windows from Unix).
I do agree that it is a difference of attitude - the Go language aims for practical usability with as few warts as possible (hence their decision to not break on Windows). The Rust language appears to be aiming for perfection (a more charitable way of saying "Ivory tower Elitists" but as we all know, perfection is the enemy of success.
|
|
|
|
|
I'm reading the Go tour, so far it looks like C meets VB6 plus something grabbed here and there. It doesn't look half bad.
EDIT: Ah. I was rejoycing too soon. In 2020 a language that forces a particular style of indentation should be hanged, burned, shredded and used as cat litter.
This
func main()
{
sum := 0
for i := 0; i < 10; i++
{
sum += i
}
fmt.Println(sum)
}
won't work because it needs those braces at the end of the line: that's what happens when you make semicolons optional.
Also, apparently there is no while, only for. So much for readability.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
modified 7-Dec-20 13:00pm.
|
|
|
|
|
|
Now if only you also learn Forth, you can go forth and do good!😂
|
|
|
|
|
Looking what "interesting" you found in THE LANGUAGE, I feel you're barely experienced developer.
First of all, "easy to build to a native Exe" is not about language at all.
Second, Go is not smaller at all - compare clumsy Go syntax with C# for surprise.
3. "Receiving data from HTTP"? Serious? THAT what makes language better? No, it's not about language as in item 1 and it's question of good library. Many languages can read from socket, not a big deal.
4. Concurrency is not a PROBLEM< it's a task. Feel the difference! Task, which is not a bit harder than sorting or queueing.
But what is really bad is that language designers drop on you all low level rubbish to handle memory (instead of SIMPLIFYING your life as it done in C#!). You think you "control memory", but no... you just dig in low level details, what is FAR from your real business task.
That's why Go even with all Mozilla's money still "nothing", but a toy for students. This language never be mainstream, don't waste your time.
|
|
|
|
|
> Quote:
That's why Go even with all Mozilla's money still "nothing", but a toy for students.
I think that if you don't even know which language you are bashing, your criticisms can be dismissed with "clueless".
|
|
|
|
|
I know where I'm wrong - actually there is two "clumsy" languages which never rise - Go(from Google) and Rust(from Mozilla). Hardly I care which made by whom. They both are dead-born.
|
|
|
|
|
I believe it is suited only for small to low medium projects. Not supporting OOP is a big limiter on the scope of the projects it supports, both in size and time. Also its best features (deferred routines, partial returns) are cool on paper, exceptional for small stuff, but try to put them in a pull request on my codebase and I will nuke it. They have the same long term issues of gotos, maintaining any codebase that uses extensively these features will quickly become everybody's nightmare.
It's a nice scripting language, but if I have to invest time and resources I will go for Python - slower, but much more likely to survive, much more supported and infinitely more reusable in other fields.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Wondering if there are as many learning Go as are learning Julia??
~d~
|
|
|
|
|
From replies, I've learned that 0 people here at CP are learning Go.
Julia probably has just as many here. But it is probably less.
Just kidding, of course. It's funny that you'll see lots of articles about languages like Go and Rust and how popular they are becoming and then when you ask people the only sound you get back are the crickets.
I wonder if it is true about Python too, because all the articles say, "Python is the only language being used anywhere at any time from now on."
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
