They were already doing this. Maybe in just some places I guess? Previously their cap was 250GB and they would call or threaten disconnect if you hit that multiple months. Then they switched to the block plan where you could go over and just get the extra charge instead of the threats. Then for a good while (up to now, last I checked) they completely put the cap on hold, I'm guessing to test how customers were impacted?? But now perhaps they're either rolling out the block plan everywhere, or just reinstating it and giving proper notice before they turn it back on. So this isn't really new, but short of providing an unlimited plan, this is a good alternative in my opinion.
This might be unrelated, but I'm constantly being prompted for captcha even when I'm just viewing and not trying to respond. Can something be done about this?
It shows up with the HN theme (orange bar at top and beige background) but without other links/text like user info on the right or the footer. I first noticed it the other day when I started using a wired connection at work instead of WiFi.
Yep. When visiting SF, I tried to walk a lot to see the city change. Going into different neighborhoods felt more like stepping into completely different cities. I'd hear X neighborhood was full of Y, and it was exactly that. Perhaps it blends more once you live there, but I was really struck by the cultural divisions.
Well after seeing those "postcards", cartoonish is becoming clearer. As a child in SF, I remember each neighborhood changing ONLY as you got to the center of each hood. There used to not be any strong demarcation lines, if that makes sense. Perhaps that's grown out of the overpopulation?
It would be nice if I didn't have to set up _another_ repo. Integrating with GitHub or BitBucket would be preferred (be backed by, not just import). That said, I wouldn't actually use it since GitHub lets you edit individual files through the UI. Just an observation. The rest looks nice though.
Right now, we integrate both with GitHub as a "Repository provider" and Heroku as a PaaS.
If you connect your Github account we'll import your GitHub repositories.
And we do have a primitive and slightly awkward way of pushing back to your github repository. That will be improved in the coming days. To make it more obvious and easier.
Thanks for pointing that out. We want to integrate as well as possible with current existing services.
There is no need to reinvent the wheel regarding code hosting and we want to focus on what makes us different.
Maybe you should allow downvoting for everyone then. I'm more likely to downvote a dismissive reply then I am to upvote every positive reply to overtake it. And on the mention of dismissive comments: as a frequent visitor I feel emotionally safer just reading and not posting... so if there is a karma threshold for allowing downvotes, I doubt I will ever hit it.
This is a great suggestion. Perhaps a good compromise would be to tie downvoting ability to a "number of days visited" threshold, rather than a karma threshold. Those who visit HN often but comment rarely may be particularly well qualified to judge whether a comment is constructive.
Edit: This might work best for voting ability in general, not just downvoting ability.
The problem is that people would abuse the downvote button and use it as a representation of "I disagree with you" is read of "this comment adds no value to the conversation."
1- Is it really a problem for the thread? If nobody agree with my comment, is it a so wrong action to pseudo-hide my comment to next readers?
2- Why users with karma will have a better understanding of downvote than the passives old-regular-readers?
Peoples who read HN every days love the high level of the comments here, let them have produce some feed back.
Note that I just defend my interest: I'm not good at creating comment with value (so I do not comment a lot), but I feel confident to reconise good comments from bad comments.
Interesting. The "reply" link is hidden for some comments - but not others - such as this one, yet I am able to bypass it by modifying the "reply" URL. Is this something new, or simply something I hadn't noticed before?
Mm, can't be that. If you highlight the area under the comment, there's a row of dashes ("-----") where the "reply" button should be. It takes up the same amount of space.
TI 57 here. Then went on with the HP-28 and HP-48. Wrote the first game using hardware scroll on the HP-48 (a Pacman).
Interesting that beyond the TI calculator, there are a few other parallels with Bellard: I studied in one of the top French engineering school (Mines de Paris), wrote a 3D program as a student (Alpha Waves, Guiness book for first 3D platformer), an open-source compiler (XL, http://xlr.sf.net), a machine emulator with dynamic translation (HP Integrity Virtual Machine, a VM for Itanium), worked on a C++ compiler (HP aC++), dabbled in Emacs (e.g. first graphical Emacs for MacOSX back in the Rhapsody days), designed or wrote some code used all over the world (e.g. modern C++ exception handling), I sometimes took really new and "minimal" approaches to old and complex problems (e.g. the scanner and parser for XLR total 1500 lines of rather simple C++ code). I keep studying physics like Bellard kept studying math, and came up with my ow wild ideas (e.g. I'm delusional enough to believe I know how to unify GTR and QM).
But there's a couple of pretty major differences as well. Bellard's work was always freely available. Except for XL, mine was mostly proprietary (and XL, an exception to the rule, was a resounding flop as far as community involvment was concerned). Alpha Waves was a commercial product. HPVM was a commercial product. aC++ was a commercial product. And today, they are all dead or dying. As for fame, I'll let you judge of Bellard's fame relative to mine ;-)
I think that there is a lesson here about the strength of openness. If you start your career, making your stuff open and sharing freely may be a pretty good move...
Hey, I recognized Alpha Waves! But I have to agree that the open approach seems to be a better career move...and maybe increasingly so these days since there are so many programmers around that if you don't open something, someone else will immediately start cloning it.
TI-82 here. I made small applications to do my 7th grade algebra homework. They took longer to make than just doing the homework, but I enjoyed automation.
While I first fiddled with a Commodore 64, my first program that I could reasonably call non-trivial was on an HP-48G. Well, I'd call it trivial to me today, but it wasn't trivial to me then.
I can't speak to the TI series, but one nifty thing about RPN is that where 80s-style microcomputer BASIC tends to afford spaghetti code, the RPN afforded breaking your program down into functions. If you didn't break it down properly, your program turned into a series of hundreds of DUP DUP + SWAP3 DRAWLN 73 SWAP DUP - DRAWLN 0x838AFE7E8A9E 3 4 108 93 BLITPIX etc etc in an undifferentiated mass. (Those aren't the real opcodes, I've long since forgotten them and won't look them up, but that's sort of trying to compute where to draw two lines then dumping a pixmap to the screen.)
Yeah, me too... TI-51 III (aka TI-55 in US) in the late 70s - belonging to my father, who had it for his job but never got to use it much because I was always playing with it. He later got me a copy of this book - http://books.google.ca/books?id=ySZhMJrzhw4C&pg=PT48&... - and that's really where my computing career began.
TI-84 here. I actually tried to get into java a few years earlier (like 9 or 10 years old), but ran into loads of problems trying to get a decent tutorial. Everything about TI-BASIC was right there in the manual, which removed all the bullshit of learning a real programming language.
I started on a TI-89, writing quizzes and quadratic equation solvers. When I got to college and found that other kids in the class had written racing games on theirs I felt like I was out of my depth - I can't imagine how the kids who'd never programmed felt.
I started on my TI-83+ and then later moved up to a TI-89, which was great for wannabe programmers because you could easily write programs in C (using TIGCC) instead of having to deal with the limitations of TI-BASIC.
