The Official Status Thread
-
Status: there's this thing called AppInventor which is basically Scratch for Android, and well, I just had to do it.
A few more touches and it will be the best Discourse client on Android available (or at least the fastest) .
-
Hey man, that looks like production quality already. Ship it, I say.
-
Status: Sitting with a glass of cider, writing a paper and read WTDWTF while the pork roasts…
-
I just implemented reading threads* so yeah, it's pretty much a complete client.
* Only first 10 posts, paging is hard. Also there's no HTML rendering so just pretend it's there.
-
EWWW APPINVENTER KILL IT WITH FIRE.
Sorry, had a automatic reaction there... Uh... Yeah.
-
Status: oh noes, Guild Wars 2 went from subscription-free to full-on free-to-play! Now Ben L will have to deal with all the riff-raff.
-
Hey, as long as your program does not need more than 2 or 3 functions, it's works pretty OK (I don't think the puzzle pieces actually help at any skill level though).
Microsoft has their thing called TouchDevelop which seems a bit more advanced, I haven't tried it.
-
Also there's no HTML rendering so just pretend it's there.
No content visible? Yeah, that'sprobablyan improvement on most forums.
-
It works but I've got a lot of problems with it. Most notably is that it compiles against API version... Like... 9 or 8 or something. So the apps it makes are using an obsolete API and look terrible...
-
And it often crashes if you try to use Bluetooth, you don't need to tell me.
Still faster for me than installing and learning Android Studio.
-
A few more touches and it will be the best Discourse client on Android available (or at least the fastest) .
Timely: https://youtu.be/MTOa2Imauqk
;-)
-
http://www.cnet.com/news/the-only-way-to-avoid-hangover-is-to-drink-less-study-says/
Filed under: Duh
-
TIL I learned that just because your code in debug configuration works, doesn't mean that your release config won't throw a mile of hissy fits.
Basically, if you use XAML Bindings then your program in debug mode won't mind if the properties the XAML is bound to are null, to be instantiated later. In release you will get null pointer exceptions for that.
I'm not sure how much sense this policy makes.
-
I learned that just because your code in debug configuration works
That a very remarkably German sentence order is.
-
But understand it you did all the same.
-
Next up: Stupid morons who "lock" their PDFs so you can't print them.
There are various pages on the net where teachers can download resources to use in their lessons. I mean, yes, I can create those myself, no problem, but do I really have to reinvent the wheel? So, what's the point then in providing those worksheets and trying to deny you the use of them in your lessons? Same goes for the idiots who set the flag to disable copy&paste in PDFs.
It's one trip to one of several web pages who will unset those flags so you can use these PDFs however you want.
And before someone asks: As long as we don't circumvent payment portals or something like that, teachers in Germany are kind of exempt from copyright issues (there are some other restrictions but those don't really matter when it comes to lessons in school).
-
Or government forms that can be filled in, printed out, and mailed, but the filled-out form can't be saved locally because it has PII that somebody could steal, or something.
-
TIL I learned that just because your code in debug configuration works, doesn't mean that your release config won't throw a mile of hissy fits.
That reminds me of the Good Ol' Days™ of Visual Studio 6. Better don't use any GotFocus event handlers at all - they work totally different in debug and production environment.
-
Actually, the first wave of newbies were all really polite. The daily achievements for yesterday included doing 4 events in one of the starting zones and people were asking for help and then getting help from other players.
-
Filed under: Duh
In other news: The sun is like...really, really hot.
I find a good Bloody Mary tends to help though.
-
STATUS: My pc after a month of redecorating.
-
Status: Reimplemented subtraction, multiplication, and division in the high level language of my compiler. Performance isn't an issue because why would someone be using BIT if they wanted performance?
-
Somehow Guild Wars 2 going free-to-play has made the ESO servers unstable. I blame Ben L.
EDIT: ESO has a habit of the server ignoring player commands for like 40-45 seconds at a time, then processing them all at once at which point it kicks you for "spamming".
-
Status:
$ wc numbers.bit 523986 131465721 681084855 numbers.bit
-
EDIT: ESO has a habit of the server ignoring player commands for like 40-45 seconds at a time, then processing them all at once at which point it kicks you for "spamming".
Are ESO servers locked to your character like WoW or do you choose them at login like RuneScape or are they abstracted away as an implementation detail like Guild Wars 2?
-
Are ESO servers locked to your character like WoW or do you choose them at login like RuneScape or are they abstracted away as an implementation detail like Guild Wars 2?
Are you asking if the servers are strongly-typed? Do you even know what that means?
-
Are ESO servers locked to your character like WoW or do you choose them at login like RuneScape or are they abstracted away as an implementation detail like Guild Wars 2?
They're completely abstracted, not even with a UI for switching instances like some MMOs have. If you're friended it just kind of silently places you on the same instance.
-
Are they running their servers on Discourse or something? Guild Wars 2 has the same setup and no problems with server-side command latency.
-
No, but they do have a few netcode bugs. It's really not bad compared to move games. Are you going to argue with me as if I ever said ESO were perfect? Because I've been complaining about it since day one.
-
-
Arguing with me seems to be the only reason people visit this forum. Especially strange when people argue with me while agreeing with me entirely.
Whatever. I'm grumpy.
-
Status: Reimplemented subtraction, multiplication, and division in the high level language of my compiler. Performance isn't an issue because why would someone be using BIT if they
wanted performancewere sane?FTFY
Why do you assume I can never agree with you?
No one else does, so it's a reasonable assumption.
-
I managed to make the BIT parser 6 times faster (6 minutes down to 1 for a 650MiB input) by removing the lexer.
-
I managed to make the BIT parser 6 times faster (6 minutes down to 1 for a 650MiB input) by removing the lexer.
TRWTF is using iB units for anything other than storage space measurements. (BTW the lack of a capslock key on my chromebook is especially annoying) But congratulations on making your compiler for a language apparently targeted at those who have nothing better to do acceptably performant.
-
TRWTF is using iB units for anything other than storage space measurements
Where are you putting your source code if it's not some kind of storage?
BTW the lack of a capslock key on my chromebook is especially annoying
Alt+Search
-
Alt+Search
Weird, that only works with the right Alt key, but thanks.
Where are you putting your source code if it's not some kind of storage?
If the distinction matters, you're already using too much of your storage and need to expand.
-
Status: My compiler is finished!
$ time coolrun hello.cool Hello, World! real 1m10.116s user 1m24.442s sys 0m0.962s
Edit:
$ cat ~/bin/coolrun #!/bin/bash -e bit -- <(coolc -o /dev/stdout -- "$@") < /dev/stdin
-
-
Because I've been complaining about
iteverything since day one.FTFY
I'm grumpy.
News at 11.
-
-
lines words bytes
35 125 733 primes.cool
565194 142159023 736513770 primes.bitHow big would you say these files are?
-
How big would you say these files are?
I would divide them by 1024*1024 and call them n megabytes, where n is the floor of the result, because I'm not anal-retentive enough to think we need an superfluous set of prefixes.
Actually, unless more precision were needed I would probably just say "about 700 megabytes." Do you know why? Because a more precise number is rarely likely to be necessary.
-
They're a lot closer to 700 mebibytes than 700 megabytes.
-
They're a lot closer to 700 mebibytes than 700 megabytes.
Only pedants care, though. And those who don't mind how silly they sound saying words like "mebibytes".
Pro tip: If you say that outside your parents' basement, you're likely to get a wedgie.
-
What forum do you think you're on?
-
Can we get an after pic?
-
Ick!
-
Only pedants care, though. And those who don't mind how silly they sound saying words like "mebibytes".
Also, while we are all pretty pendantic round here, we hates the word “mebibytes”, preciousss, we hates it forever!
-
Can we get an after pic?
The second one is halfway through cleaning.
The "after pic" is a clean motherboard and components. You expect something special?
-
Maybe a gun-shaped heatsink?