5,145 karma · joined April 6, 2010
Perhaps the same people responsible for the file system engineering are also responsible for developing this user-facing application. They might excel at low level system engineering, but they are utterly unqualified to develop a high level GUI application.
Spend 5 minutes with the app and you'll find a half dozen bugs and amateurish mistakes. It's baffling, and it's been a problem for two years now.
https://i.imgur.com/VE7kEeC.png
"debo" must have been an intern.
Years ago I moved all of my important passwords to a secondary keychain that remains locked for precisely this reason.
Beyond that, it's pathetic click-bait.
I think I could get used the keyboard overall, but the arrow keys (with full-height left/right keys) were a complete no-go. There's so little space between each key I found it impossible to position my hand over the arrows properly.
I was completely ready to buy a new MBP but those arrow keys put an immediate end to that thought.
https://youtu.be/6tUWoy1tJkE?t=45m
The Pascal bits are from 45:00 to about 50:00.
...
My manager at the time said, no, we don't want to do this [Pascal],
people are happy with what they got. I overrode him and went to
Jobs, and Jobs said "Well, I'm not convinced. I think our users are
happy with BASIC and assembly language. But you seem passionate
about it. I'll give you one week to prove me otherwise."
I was on an airplane within two hours down to UC San Diego and I
started porting right away.
...
The other thing that happened then is I had to plug in the disk
routines, and their system was pretty big and that little 13-sector
floppy disk didn't have a lot of capacity. Well, Woz had just come up
with a different way of encoding the data on the disk so that we could
get more data for the same disk size, and we needed the 16-sector disk
routines. And so Woz came down, and I was there... I had never bothered
to get a motel because I slept on the bench when I wasn't working. This
is in the computer science lab at UC San Diego. I was busy, I didn't
have time to go sleep.
But Woz came down, and I got to interact with him and it was really fun
because he was working on installing these 16-sector disk driver
routines, and he'd go 'type type type type type' -- and he didn't type
in assembly language and have it assembled. No, he'd type in 6502
machine code. Hex. -- He'd type in hex, and then, you know, watching
him type and he'd go 'type type type' -- pause -- 'type type type type',
and when he finished I asked him what was the pause? And he said
"forward branch, seven instructions, I had to compute the offset before
I continued". So, he didn't back-patch the offset, he actually looked
at what he was going to be typing, knew how many bytes it would take...
he was brilliant. From: t-jacobs@utah-cs.UUCP (Tony Jacobs)
Newsgroups: net.micro.mac
Subject: MultiMac MULTITASKING!
Date: Thu, 21-Nov-85 12:12:47 EST
...
It doesn't work with some programs (like MacPaint)
and some apps need to be the first app loaded to work
(like MacDraw.) When you run multiple sound apps the
first one run is the one that works, the rest will
run but you don't hear a them.
...The compiler can't do that automatically because the any method and any class can be replaced at any time. Key-value observing is a common feature that replaces method implementations on the fly at runtime.
You can buy the most-recent version of app on your computer using iTunes (or a newer iOS device), and then download the last compatible version to your iOS 6 device.
http://i.imgur.com/UJFM9vA.png
I was hoping to see some awesome <layer> tag action, but it wasn't to be.
For the better part of the 20th century we used mercury-vapor street lights, which bathed the streets in soft blue light. The complete lack of red wavelengths in these lights would make a red car look black, and made humans look like vampires.
The animals and the humans will be just fine.
Are there technical reasons why Microsoft didn't release a Protected Mode version of MS-DOS in the 80s, or was it just a case of trying to push users and developers to OS/2 and Windows?
It seems like such a no-brainer, especially since MS-DOS provided so few services to applications anyway. You have MS-DOS 8 and MS-DOS 16, and you let the user choose which version to boot into, or you automatically kick over to MS-DOS 16 when a Protected Mode app is launched. It seems a lot saner than forcing users to muck around in config.sys.
That people were forced to deal with the memory limitations of the 8088 PC well into the 90s is just bananas.
It's crazy that Google isn't investing that money in software. Unless it's a hedge.
The equivalent Go code would then (presumably) be these two methods:
func drop(seq []T, while func(T) (bool)) ([]T)
func dropWithError(seq []T, while func(T) (bool, error)) ([]T, error)
If you pass in a closure that throws (i.e., can return an error) then the compiler will require try/catch error handling at the `drop()` method call site.If you pass in a closure that does not throw then compiler will assume that `drop()` does not throw.
But in my neck of the woods we'd probably show a green right arrow when intersecting traffic from the left is stopped at a red light.
> by controlling the stagnation of web browser tech, they can force
> developers to implement apps with their high-lock-in native app
> frameworks
Ah, web-developer logic. Always good for a laugh.Yes, if Google were allowed to distribute their fork of the WebKit engine on iOS then everyone would stop writing iOS apps. Just like no one writes Android apps.
And it works with C Blocks!
typedef int IntegerProcessor(int);
int executeTheFunctionPointer(IntegerProcessor* function)
{
return function(23);
}
int executeTheBlock(IntegerProcessor^ block)
{
return block(32);
}
int doubler(int a)
{
return a * 2;
}
int main(int argc, const char * argv[])
{
IntegerProcessor* myFunctionPtr = &doubler;
int a = executeTheFunctionPointer(myFunctionPtr);
printf("%d\n", a); // 46
IntegerProcessor^ myBlock = ^(int b) {
return a * b;
};
a = executeTheBlock(myBlock);
printf("%d\n", a); // 1472
return 0;
}
My mind is completely blown.The headline is absurd. The article is absurd. Everything about this is absurd.
I like the feel of the keyboard, but I found absolutely no way to orient my fingers over the arrow keys. There is no way tell whether I'm hitting the up arrow or the right shift.
As someone who works with text, it's a deal breaker for me.
48 MB of code and frameworks (including 10 MB for Swift).
4+ year old iMac with dead video card. I took it to the local authorized Apple dealer, who wanted $50 to diagnose the problem.
Dealer called back and said Apple agreed to replace the video card for free and cover the $50 dealer diagnosis fee.
In this case, the battery manufacturer couldn't meet these particular design constraints.
Incidentally, remapping Caps Lock to Control on that keyboard required a soldering iron and a pair of side cutters. But it works.
The pictures of screen look unusual, as if every second scan line is missing. Is the Alto outputting an interlaced video signal? That would be very interesting and unexpected.