mschaef

35 ms·

301.
by mschaef 7y ago
> git was a major step back in usability for my group from bk to git. What does that mean in concrete terms? What are the failures you're seeing with git that you weren't with bk? How long has your team used git? bk?
302.
by mschaef 7y ago
> I hope it's the last DVCS, The only reason I'd disagree is if the next source code control system were somehow as much an improvement over git as git was over its predecessors. > if it can save me the hassle of learning a
303.
by mschaef 7y ago
> If its interface is not simple and elegant, I don't see how you can call git simple and elegant, since it's how all users will interact through the interface. At least in my experience, the interface makes a lot more sense if
304.
by mschaef 7y ago
It really depends on the target platform, who will wind up maintaining the code (and for how long!), and how the build will be done. But the short version is that I would (and do) favor Clojure for personal projects. These are cases where I
305.
by mschaef 7y ago
> Plus lots of contracting in the 80s for people who needed data (send back and forth on floppies) converted from one accounting system to another. When I was sixteen or seventeen, I worked as a summer intern in the IT department of a lo
306.
by mschaef 7y ago
> You have to see this in historical context. That Basic had an editor was a huge step forwards. That it wasn’t a full-screen editor was because full-screen editors didn’t exist yet I (mistakenly!) edited out the part of my post that cla
307.
by mschaef 7y ago
I managed to avoid most of that, thanks to a bit of sheer, dumb luck. Back in the early 80's, my elementary school piloted a program (inspired by Seymour Papert, I presume) to teach school age children to program in Logo. So we had a l
308.
by mschaef 7y ago
> I understand the arguments against BASIC, e.g., ingraining impractical paradigms, The early interpreted BASICs did make it difficult to write good code. All source editing was line editing, every line was numbered, there weren't a
309.
by mschaef 7y ago
> far less wasteful of cornea, The argument years ago that convinced me NOT to have this procedure done was that they'd have to remove fully half my cornea. I'm assuming there are ways to recover from that with a corneal transp
310.
by mschaef 7y ago
I mentioned you in a peer post that you might not otherwise notice. https://news.ycombinator.com/item?id=21529637
311.
by mschaef 7y ago
Not bad... as saagarjha says, you can slide on either that key or the brightness key. Unfortunately, that doesn't work for me because I've set the touchbar to default to F-keys for the sake of consistency with the other keyboards
312.
by mschaef 7y ago
I've had a touchbar machine as my primary for a couple years now and essentially don't use the touchbar. But I didn't use f-keys all that much either. I think there are some software improvement that could maybe make it bette
313.
by mschaef 7y ago
Or even both the touchbar and the physical keys on the pro models? 7-row keyboards are a thing.
314.
by mschaef 7y ago
It takes a long time to get a design through the point of manufacture... especially at that scale. And even before that happens, an organization needs to admit that it has to happen in the first place. For everybody saying the keyboard suc
315.
by mschaef 7y ago
I think you're saying the same thing. A one-time 20% bump isn't worth that much these days to the vast majority of people. (Even if it is only 10 minutes... which I tend to think might be an underestimate, given the testing, etc.
316.
by mschaef 7y ago
What does that look like from a data structure perspective? Each grain has a bounding box and you only look at the geometry for that grain if a ray crosses the box? (I'm way, way out of my wheelhouse here, if it's not already obvi
317.
by mschaef 7y ago
Funny you mention that, but one of the better pieces of MFC related advice I read was to have a single central location for computing UI element states. It did feel a lot like React does these days (albeit with less sophistication in the un
318.
by mschaef 7y ago
> at the 10K foot level the model was the same - input loop, window messages, and window procs. That's a fairly broad description, isn't it? At least I have a hard time coming up with windowing API models that don't fundam
319.
by mschaef 7y ago
> However, when the partnership fell apart, Microsoft just took big chunks of that OS/2 API and created a sub par version and called it the Windows API. Microsoft learned from the mistakes IBM forced on them and did a better job. Ri
320.
by mschaef 7y ago
Sort of. IBM really wanted to ensure that OS/2 had an imaging model that was compatible with what it used in some of its larger computers. This resulted in a bunch of differences between OS/2's imaging model and GDI. (Differe
321.
by mschaef 7y ago
> By the requisites they list, which focus on the ISA, the original 68000 was already a 32bit architecture in 1979, Huh? The second paragraph states: "First, let's define our terms. A 32-bit microprocessor has a full 32-bit arc
322.
Dtack Grounded (1981-85)(easy68k.com)
1 points by mschaef 7y ago|0 comments
323.
by mschaef 7y ago
> Win32, especially when it comes to GUI programming, is one of the worst APIs out there. It's also one of the first. Win32's origins extend back over 35 years and start on machines with a tiny fraction of the capability of eve
324.
by mschaef 7y ago
Agreed... it's easy to envision scenarios where Linux would have fallen off completely back in the 90's. (After all, Linus' original goals were 'better than Minix' and 'learn about the 80386').
325.
by mschaef 7y ago
> I have more respect towards Apple than to think that the current state is the best they could do. $265B in Revenue and and $59B in profit seems to indicate they're already doing pretty well. Maybe your definition of 'best&#x2
326.
by mschaef 7y ago
I'm pretty sure this hasn't been true for 20 years. Tcl 8.0 introduced a form of byte compilation. [1] While the comments might slow down the compilation a bit, I doubt they have any impact at runtime these days. 1] https:/&
327.
by mschaef 7y ago
No worries... I figured it might be something like that.
328.
by mschaef 7y ago
> You said "this is why FP sucks". No, I did not.
329.
by mschaef 7y ago
> Once you've arrived deep into diminishing returns you can stop increasing the spending. How do you know they're not there now? It's hard to believe they're not thinking very carefully about these sorts of things, gi
330.
by mschaef 7y ago
> Either way the point is that Apple should be concerned about quality of software far more than it is. I submitted a bug to Apple about how the Apple login page was rejecting requests from browser headers from Linux machines. ... Apple

More ›