131–138 of 138 posts
Sad to say the book isn't on Library Genesis, so you'll have to drop $40 if you want the knowledge. http://libgen.io/search.php?req=little+typer Also Library Genesis is amazing: http://libgen.io/search.php?req=knuth It's everything I dreamed of when I was a kid. I used to spend hours at the local library scouring through crummy "Learn C++ in 24 hours" type books. http://custodians.online/ is worth a read too.
Sad to say the book isn't on Library Genesis, so you'll have to drop $40 if you want the knowledge. http://libgen.io/search.php?req=little+typer Also Library Genesis is amazing: http://libgen.io/search.php?req=knuth It's everything I dreamed of when I was a kid. I used to spend hours at the local library scouring through crummy "Learn C++ in 24 hours" type books. http://custodians.online/ is worth a read too.
I feel like there’s so much to say about this comment, that I don’t even know where to start. So firstly I agree, $40 seems like a lot. I personally couldn’t justify it at the moment. Particularly when the reproduction cost is nearly zero. But $40 also doesn’t seem like a lot to pay for a book that will probably not sell more than a few thousand copies. Most likely revenue generated won’t fully cover the time and eff…
This is published by MIT press, but the author (Friedman) is a professor at Indiana University.
Earlier quoted context omitted.
> Network stacks, databases etc. that correctly handle trillions of interactions, But they have also incorrectly handled a similar order of magnitude of transactions! Routing failures and issues that people troubleshoot around, misconfigurations and bugs, and simple electromechanical glitches exist in the real world and they're not some kind of zebra, you can force them by pining a server. Our networking systems "mos…
Again lots of interesting points. Only time for one response. You highlight networking but I also mentioned databases. Schematizing your comment "Our... systems "mostly work" because... the difference between a perfectly coordinated... system and a purely chaotic... system... is actually rather small". I think banks and customers would disagree rather violently regarding the (distributed, asynchronous) system that ha…
Do they? Most customers accept without question the idea that they have an "available" balance distinct from their "current" balance.
It's also the case that when attacked the system typically fails and then the fungibility of currency combined with the massive power of insurance is used to pave over it.
Earlier quoted context omitted.
It's not even really possible to "adopt" dependent typing today. It's only emerged from the realm of academic curiosity and only two implementations exist that are anywhere near "practical" in the context you're describing. Both of those implementations are very honest about their shortcomings, and nearly every talk and blogpost for them mentions you can't yet use this in many industrial contexts. It's very difficult…
>only two implementations exist that are anywhere near "practical" Out of curiosity, why F* or Idris are not practical?
What did you think I was imagining? I can only name 5 DT languages off the top of my head.
I'm going to order it right now. I highly recommend the little schemer and the seasoned schemer too! I have read all the titles (MLer and Java too) in the series and those are my favorites. The only one I have not finished is the reasoned schemer although I hope to try again in the future.
I am just now (as of reading your comment) becoming aware of the "Little" series. Is there a particular order in which one should read the books?
Earlier quoted context omitted.
>only two implementations exist that are anywhere near "practical" Out of curiosity, why F* or Idris are not practical?
F* and Idris are precisely the ones I had in mind, although I guess you could make an argument for Agda. What did you think I was imagining? I can only name 5 DT languages off the top of my head.
Earlier quoted context omitted.
If I understand your position correctly, you feel that even if someone does not have $40 or would not have paid $40 for something that can be freely copied, it is both immoral and unethical to ignore the author's wishes and copy it anyway. Even though you as the author are unaffected by this action. You also feel that it's justifiable to seek out people who do this and tell them that they should not do this, i.e. how…
How is this victimless? I write a book, put it out on the market. Someone copies it and puts it up on a website (crime alert). Someone like you publicises it. I don't get paid because from your point of view, it is out there free for the taking. Meanwhile, I have lost hundreds or thousands of potential sales from people who may have paid, but have now been tempted to join your illegal caper. Everyone revels in the ve…
No you haven't, and there lies the crux of the argument. Many of those who helped themselves to the free copy wouldn't have purchased it at the retail price anyways, even if there were no free copy to be had. There is a financial loss yes, but multiplying the total number of free copies by the profit to the author off purchased copy yields a greatly exaggerated figure.
Earlier quoted context omitted.
How's it "not knowing the difference" to explain that the usage of the terms client and server switched over time, in the sense of which is local and which is remote? An xterm client running on a VAX mainframe connects to an X11 server running on a Sun workstation: the X11 client is remote, the X11 server is local. A web browser client running on a phone connects to a web server running in the cloud: the web client i…
Exactly! I, too, used to live in an office next to a machine room full of "web clients"! :-D (Actually, I'm one of those deluded fools who claim a "server" provides a "service" to one or more "clients", who make "requests". Yeah, I know, but I figure somebody has to keep the joke funny.)
https://www.quora.com/profile/Jim-Fulton
https://www.quora.com/Why-is-the-X-Windows-architecture-clie...
>Given it's roots, X naturally used the technically-correct terms to describe its major components: the portion that abstracted display and input hardware into a service that could be used by other programs was called the "display server"; the portion that made use of those services was called the "display client." This later caused endless confusion who thought that "server" was a synonym for "big computer" (file server, database server, etc.) and "client" meant "small computer" (diskless client, etc.). Who knows, maybe it would have been easier had they been called "application server" and "application client" but that revisionist history.
Also interesting:
>Ultimately, the pendulum swung back with the advent of Web 2.0 technology and mobile devices. Now, we take it for granted that applications can run anywhere in the network and be accessed by any type of device. While X is primitive compared to JavaScript and HTML5 (whose ability to push computational tasks over the network into the display device were inspired by Java and NeWS), X did lay the initial groundwork. It also proved that an open source model could work for in business environments. Not too shabby for a technology that will soon be hitting its 30th anniversary.
>Jim Fulton, alumnus of Project Athena, the MIT X Consortium, Cognition (first commercial use of X on DOS) and Network Computing Devices (leading X terminal vendor)