uglycoyote's comments

This looks neat. I'm interested in some of the more advanced exercises like the Rick Beato one here (https://app.captrice.io/?eid=ph79of6zlotm8y24mc4) but a couple of things prevented me from truly attempting it:

Firstly, the tab for that exercise is long enough to need a scroll bar, and so I don't understand how one is supposed to play along with that tab to a metronome... am I expected to operate the scroll bar every couple of measures while still staying in time with the metronome? So I would suggest either auto-scroll, or better yet just find a way to get all 12 measures of the exercise to fit on the screen at the same time. I have a big enough monitor that it would fit.

Secondly, although you have the link to the embedded video player, I wouldn't be able to keep the intended sound of the exercise in my head long enough that I would feel confident I was playing the exercise right later. The app really feels like it needs a synthesized guitar sound that would play the notes of the exercise, so that I could play it along with the synthesized version and know whether I was hitting the right note. It would be OK if it sounded cheesy -- that would be better than nothing, and then once I was confident that I had the correct sequence down, I would disable the synthetic sound.

yes, the title of this post should be, "Zed, a collaborative Mac-only code editor....". I also find it kind of obnoxious that their front page says they are focused on making the world's best code editor without mentioning that it is tied to one platform. I don't think it can come close to being the best editor with such limitations.

I'm a game developer but not specifically a graphics programmer. Although I work with modern graphics APIs and GLSL shaders in my day job, when my 13 year old recently graduated from wanting to program in Scratch or Python to wanting to learn C++, I decided the best thing to do was break out the old OpenGL 1.2 DLL's that I still had on my machine since 1999 and starting him writing some code using glut and glbegin/glvertex/glend type of immediate programming.

it is just a lot more fun than trying to suffer through all of the setup that one needs to do with modern APIs. he is more interested in computational geometry type of things like voronoi diagrams so the graphics API is really just a means to an end and fancy shaders and lighting aren't important right now, and performance in C++ and old school OpenGL is about a thousand times faster than Scratch, so I think we hit a sweet spot for where he is at in terms of his progression of learning.

even with the simplified API of OpenGL 1.2, he is still biting off a pretty ambitious chunk of learning to try to grasp c++ at the same time as OpenGL, so the simplicity helps keep it sane and manageable, and things are going well. He did some neat marching squares demos and I helped add an IMgui menu to tune parameters at runtime. it has been entertaining!

which is why the title should have been "discover volunteer opportunities around the US"

if you're targeting enterprise clients, they may insist that your course fit in to their existing LMS (learning management system). A bunch of large corporations use these old and stodgy technologies and require learning materials to support the ancient SCORM API or the slightly less ancient xAPI API. You might find, if you go that route that you spend more time dealing with the complications of improperly implemented APIs, poor developer documentation for integration into those systems, organizations who don't really have people with the technical knowhow to help with the integration issues, Subject Matter Experts who aren't actually experts at anything, etc., and less time developing your own technology.

Compilers have always been making guesses about what the most likely code path is behind the scenes, but it still needs to behave correctly in the case where it was wrong (that will just be the less-optimal code path). All these attributes are doing is helping the compiler know instead of guess what the hot path is. if there is any way to confuse the compiler into giving undefined behavior with hints like this, that's a compiler bug. (not saying compiler bugs don't exist, but are you aware of a specific bug like this)?

this resonates with me.. I fell in love with python because it made it really easy to write 100 to 1000 like I scripts that I could whip out in no time and make something happen. I still love it for that. But I fell out of love with it working on a large codebase -- mostly someone else's code -- where I felt imprisoned by not knowing the types of most function parameters, what I could do with those types, and what code I could change without breaking other code. The lack of ability to navigate in the way that I can navigate C# or Java killed python for me

I still have to use python though. I make an effort to type-annotate everything I see, and python's type annotation features keep improving, but it still often feels like an awkward uphill battle

hmmm.. they don't seem to really explain the rules of the game here. Doesn't the length of time it takes to crack a password depend on the rate at which you are allowed to try different guesses at the password prompt, and whether or not you get locked out or penalized with delays after a certain number of wrong guesses?

When they say it takes 48 minutes to "crack" my password are they assuming some specific rate at whichever the system they are trying to log in to responds to failed login attempts?

Very frustrating article to read. The article is setting up a straw man and attacking it. He is acting like everyone else thinks:

1) edges are the only important features in images and 2) line drawings can only represent edges.

Who are these brainless absolutists that he is attacking?

Then he's acting like he is the only one with other bright ideas that nobody will listen to.

I think it is obvious to anyone who thinks about this that:

1) edges are a useful feature for recognizing objects in images but not the only useful feature 2) lines in line drawings can and often do represent edges, but there are a lot of other things they can represent. Light and shading and texture of various kinds.

It would be fine to write an article that goes in to depth on the different nuances, but it is annoying that this author pretends that most other experts have naive and simplistic views, with "uncritical certainty", and "no one seems to question it", and the author "has a hard time convincing them otherwise". It is a very condescending tone that comes off sounding like the author is presenting themselves as some brilliant but misunderstood outcast, and the only one who can see the light of truth.

we could do without the drama!

I'm in the field but don't actually use USD so when I heard some colleagues talking about it I googled to try to figure out what they were talking about... but was unable to find anything that wasn't talking about currency. Even if I Google something like "USD format converter"I tend to get a bunch of currency converters. it is kind of a pain in the ass.

it seems to me, if there is one discussion forum where you should be able to point out that a website it broken for technical reasons and why, it is HN.

I found this comment interesting (because it explained why the content was completely unreadable) and useful (because the sub comments lead me to a solution that allowed me to read this content).

I can't tell if that is the case here, but a lot of time it is the original author posting their content on HN because they want feedback from smart people, so hopefully this is useful to them as well and they unbreak their website.

Please consider revising this rule. It seems like such complains should be allowed when the website is completely unusable.

in my experience HDMI works better. I have had Dell 4K monitors both at my home and my work, on three different PCs all have the exact same issue: with DisplayPort I can't get more that 30hz and the mouse is so delayed that it is practically unusable. I almost sent the first monitor back, but when I decided to try the supposedly-inferior HDMI I had no trouble driving it at 60hz and the mouse movement feels buttery smooth (no latency). it's not a case of a weak video card... my card at work easily drives two of these 4K screens at 60 hz over HDMI but for some reason can't drive a single 4K monitor at more than 30 on DisplayPort. what's up with that?

I was disappointed in that example for a different reason. it ran on my phone, but when I pinch -zoomed (which is what I assumed a zoom widget built for web was supposed to support) it kept zooming towards the same point, which was a boring black spot. it didn't pan and zoom like I would have expected.

I think you still need to explain further. it is not clear why you think the author is being annoying. it sounds like you are agreeing with the author in your last sentence. I'm confused.

> in context learning using large language models

In which context is it learning the language models of what?

If it's learning the language models using a different context than the context of the company I work for, then it's learning not learning anything relative tho the codebase that's important to me. So what use it is?

Generally speaking, companies have their own libraries and their own style of coding. Having a language model of how someone at facebook is coding their javascript isn't going to help me at all with generating useful completions for my FORTRAN code against some 20 years of legacy code on my company's own codebase. But training it locally on the 20 years worth of legacy code sounds useful.

I'm confused about the premise here. The power of self-hosting such a thing is presumably that you would be able to train it on your own company's codebase as a corpus of examples to help other people in the company know how to navigate the specifics of your codebase.

But there's nothing in the introductory materials about how to train this thing.

I'm confused... you are right that it takes no additional torque to keep a frictionless rotor rotating at the same angular velocity, but in the real world there is friction and air resistance where you have to keep applying torque to keep something spinning at the same rate. and if you are applying torque to someone, then that thing is applying an equal and opposite torque back... is it not?

regarding accessibility..from what I have heard, other cultures have much different styles of sarcasm which might impede their ability to understand that something you have said is sarcastic. e.g. Japan is known to have a reputation of not understanding American sarcasm, but has it's own style of sarcasm. (see https://linguaholic.com/linguablog/sarcasm-in-japanese/)

so, I guess announcing your sarcasm makes sense in an international accessibility sense, particularly when some of the normal cues are not present (tone of voice, facial expression, eyes rolling)

I find if you avoid the use of any function that has the word use in it, react is a lot more useful and usable.

I live on the opposite planet. basically every bug that I have ever had in python over my 15 years of using it has had to do with a type issue. So the increased use of types and python and ability to express type concepts in python is the thing that I'm most excited about.

it is not necessarily about type mismatch bugs per se, but more like without type information in the code I will misunderstand what kind of structure is passed in to a function, how to decompose it, what members the data has, what functions does it have, how do you spell them correctly, what elements to expect in dictionaries and what kinds of values do they have, and how can I make massive changes to code without knowing all those answers and expect it all to still work.

type annotations are solving a lot of those issues for me nicely, and the number of things that it doesn't solve well is decreasing with each version and the new features they are adding