_yawn

Email is a cesspool, this is a genius idea.

People in Quebec are actively hostile to other languages in general, mostly for historical reasons. Probably not the best place to get started haha

I honestly can't tell if this is a shallow dismissal or if you are proving your own point by being the most upvoted comment.

I feel like a lot of users on HN are producers rather than users of software, and haven't used node-based systems like in blender or nuke. They are extremely productive, and end up being very similar to functional programming while being super easy to pick up. It's a great "inbetween" representation for non-programmers that really need to do domain-specific programming.

What we really need isn't more syntax, it's core features like threads, operator overloading, a large std library, some real form of serialization (JSON doesn't come close to counting), etc.

> They may not even be capable of it.

Come on now...

Like all "theories" of art and music this model is no good as it isn't predictive. There are plenty of good art with brightly saturated color. Deciding spontaneously that muted colors are the one true way and then that preference for saturation is some sort of retardation in development is just laughable at best. I have a friend who prefers muted colors precisely because he's color blind.

That's very true, videos that record powerpoints are also often hard to read.

That's an interesting study. I feel like maybe engagement is the wrong metric, much how like A/B testing gives a good local result but a poor global result. I finished a dozen or so of the traditional courses but can't be bothered to complete the split up ones. I'm surely not the only one.

I'm going to go against the grain here but just putting cameras in classrooms and dumping that on Youtube works just fine. The content on MIT opencourseware feels a lot nicer than things like Coursera or others even if it's more traditional. At the end of the day you just want to communicate efficiently, and imperfect access to information is a lot nicer than no access. Don't sweat the details.

It's because designers are just clueless and don't know how things are implemented. The opposite is also true: the parent is practically an alien here for liking design yet he doesn't even see the point in a photoshop over a wireframe.

I think in general people are too specialized. You probably want designers that do a little development and developpers that do a little design. The full on generalist approach is also poor, I've done both jobs in my life and ended up mediocre at both.

What problems do you run into? I'm familiar with lisp's macro system but didn't get to look into hygienic macros in other language, and was wondering if they are equivalent.

Why not just include interactive exercices/puzzles into the html documents? I took a db course not to long ago and would have loved it to be more "hands on".

This is really nice and looks great. The diagram is super useful and I could see myself using this for the rough planning of an app. That being said, I feel like like the use cases are super limited unless you flesh it out some more. There needs to be a way of encoding more information about state, maybe scoped variables that you can modify on events or something!

:)) I love macros so much

I mostly miss them for constructing objects with default values, yes. The alternative is the builder pattern, which involves a lot of boilerplate.

Skepticism towards keyword arguments is something I have trouble understanding. Is it because of some performance consideration?

Thanks for your answer!

This is unrelated, but do you know if Rust's omission of exceptions is a consequence of the borrow checker, or an explicit design choice? I get that most people come to Rust from C++, but as someone coming from a higher level down to Rust, things like the complicated error handling and lack of keyword arguments bother me.

Subjective != arbitrary.

You can have lots of expressivity without having that many features. But go has neither, and things like no operator overloading just plain sucks when dealing with vectors, for example.

Do you mean winner in terms of popularity or in terms of quality? In terms of popularity, it's pretty clear we are in for at least a decade of C++ & Javascript.

Content and presentation both change, and together. That's how it's always been for every type of media. How much space you have on the newspaper determines what your article's title is, but what the title is also determines how much space you have.

The whole point of abstract data types is to separate implementation from interface in order to allow a change in representation.

The point is to allow programming things like the AI algorithm without caring at all about if the board is represented with a hash map, nested arrays, or a bitboard. In all cases, all the AI cares about is move generation, not internal representation.

Abstraction does not hinder ideas like the bitboard, it enables them. Both the interviewer and the interviewee are missing the point.