The Official Status Thread
-
@dkf said in The Official Status Thread:
@Benjamin-Hall said in The Official Status Thread:
Tiny kitchens walled off from the rest of the living space.
That's not necessarily bad. It's very nice to not have the rest of the property smell like frying.
That requires more than just walls, it requires significant doors. And that's obnoxious. It means that you can't see what's going on outside this tiny room (so social stuff while cooking is out), you can't carry food easily between rooms (so entertaining is out), and it's just generally a hassle.
Now if you have a much larger space and can have a dedicated large-size kitchen with an attached, single-purpose dining room, then sure. But a better strategy is just have adequate ventilation in the kitchen. Which is required by most building codes (but rarely if ever enforced), and also something these kitchens lack.
But really, the lack of counter space is my big gripe. You've got enough for a pizza box. Total. That's not enough to cook anything that requires, like, ingredients on.
Edit: I can understand this kind of micro-kitchen in a NYC apartment. Or a Tokyo one. But in a relatively rural area (town of 60k spread out over many many square miles)?
-
@Benjamin-Hall said in The Official Status Thread:
But really, the lack of counter space is my big gripe.
Can't have too much counter space. Or too many cupboards and drawers. Or too much fridge and freezer space.
-
@dkf said in The Official Status Thread:
@Benjamin-Hall said in The Official Status Thread:
But really, the lack of counter space is my big gripe.
Can't have too much counter space. Or too many cupboards and drawers. Or too much fridge and freezer space.
Agreed. In college I lived in 6-person (3 bedroom) apartments. Even if only a couple of us actually cooked, there wasn't nearly enough space. Dishes alone took up about 1/6 of the space (1 cabinet), and only some groups of people were capable of sharing food without it causing issues, so you had massive redundancies in supplies. It sucked.
-
@dkf said in The Official Status Thread:
Can't have too much counter space.
I've got 160cm+60cm+80cm and I don't see need for more.
@dkf said in The Official Status Thread:
Or too many cupboards and drawers.
When I replaced my kitchen 1½ years ago (is it already that long since I signed for that?) I actually eliminated overhead cupboards on one side to make it feel less cramped. Though my kitchen is laid out with two 3-meter stretches on each side of a 1m40 wide aisle, and I did also replace all the under-the-counter cupboards with drawers, so I've still got huge amounts of room.
@dkf said in The Official Status Thread:
Or too much fridge and freezer space.
And that's where I went wrong. I used to have an under-the-counter freezer, which was tight but manageable, and thought modern freezer with more efficient isolation would improve matters. They did not. I should've gone for separate fridge and freezer side-to-side, rather than a combined model.
I still don't miss the microwave; just about everything it could do the steam oven can do better.
@Benjamin-Hall said in The Official Status Thread:
But a better strategy is just have adequate ventilation in the kitchen.
scribbles Has never lived with anyone with less-than-perfect hearing.
-
Status: Why do I even try logging in to wow 9.0 PTR first day it's open, when I know in advance it's a shitstorm and the ptr character server can't take the load.
-
@dkf said in The Official Status Thread:
the house that took up residence in my desk lamp
-
@HardwareGeek said in The Official Status Thread:
@dkf said in The Official Status Thread:
the house that took up residence in my desk lamp
you need to rewind the stack a little more.
-
Literally every other website to ever exist: "Private Message"
Big brain Twitter: "Direct Message"
-
@Tsaukpaetra said in The Official Status Thread:
@HardwareGeek said in The Official Status Thread:
@dkf said in The Official Status Thread:
the house that took up residence in my desk lamp
you need to rewind the stack a little more.
Oh, I know what he was trying to say, but it's not what he actually said. Switch the order of the subordinate phrases/clauses, and it makes sense. As written, the clause "that took up residence in my desk lamp" modifies the house, not the wasp.
-
@HardwareGeek
Pretty sure you were ’d in the QooC thred
-
@anonymous234 said in The Official Status Thread:
Literally every other website to ever exist: "Private Message"
Big brain Twitter: "Direct Message"Literally every other website to ever exist at the time: "Upvote"
Big brain Facebook: "Like"
-
@izzion said in The Official Status Thread:
@HardwareGeek
Pretty sure you were ’d in the QooC thredI know, but a must .
-
Status: Finally escaped from the Humble Bundle not-really-a-subscription. It only took six rounds of "Find the Cancel button."
-
@Parody
I'm sure they'd take a PR to add a 7th
-
@izzion said in The Official Status Thread:
@Parody
I'm sure they'd take a PR to add a 7thFinding the Cancel button automatically triggers it.
-
@dcon said in The Official Status Thread:
@izzion said in The Official Status Thread:
@Parody
I'm sure they'd take a PR to add a 7thFinding the Cancel button automatically triggers it.
This smells of a certain H2G2 idea...
-
Status: the constantly repeating weird sounds/music outside of my window make me wonder if Mario escaped out of a video game and there's some real-life mini-games going on.
-
Status: Found a bug in Python today that I know nobody will ever fix.
You wanted to know more?It's a wrong word in some docs — earth-shattering, I know — and the reason it'll never be fixed is because it's only present in 2.7, which is totally EOL now and we only support it because of slowpoke collaborators of ours.
The equivalent in the current source does not have the bug.
-
status: started playing an embedded video in a thread. Moved threads. Normally this deletes the element (and videos) therein, but several threads later I saw I could resume playing from the notifications thingy.
GG Chrome.
-
Status: Updated our software to support the current production release of Python. The version after looks like it is going to be a pain though, as some of our critical dependencies appear to do things that are deprecated. Can't do anything about that though; putting our own house in order was more than enough work for today…
Can't wait until we can stop supporting 2.7. Then I'll be able to delete so much crap…
-
Status: Tired of having to choose between chocolate milk and Froot Loops and losing weight.
-
-
Status: About halfway through the massive gathering project toward Best In Slot
-
@izzion I was spamming collectables for scrips. But then the lag was so bad (2-3 second spikes unpredictably) that my macros were randomly failing. So now I'm going to bed.
-
@Benjamin-Hall
This is why you don't craft in Eulmore.
-
@Tsaukpaetra said in The Official Status Thread:
@Zenith said in The Official Status Thread:
chocolate milk and Froot Loops
:holdup.png:
I don't put the Froot Loops in the chocolate milk.
-
@Zenith said in The Official Status Thread:
@Tsaukpaetra said in The Official Status Thread:
@Zenith said in The Official Status Thread:
chocolate milk and Froot Loops
:holdup.png:
I don't put the Froot Loops in the chocolate milk.
Oh okay.
-
status you know that something has gone horribly wrong in your life when you install a new OS and you actually find yourself getting enjoyment out of using it.
lubuntu for those who are curious.
-
@izzion wasn't just there. I think the problem is that my connection is a crap DSL link shared by 3 others who like to stream videos. And the modem is a potato. Oh, and I'm on wifi, as all of us are.
Can't wait to move out and have my own place. End of the month.
-
I hate how functional modern programming languages have become.
I can understand "get X, then do this and that, then return Z".
I can't understand "get X and return a function that will get a function ZReceiver and do this and that and then call ZReceiver with Z".
-
@anonymous234 said in The Official Status Thread:
I hate how functional modern programming languages have become.
Did you mean: asynchronous?
-
Status: Raw input acquisition completed. Commencing regeneration cycle to minimize risk of catastrophic mistake.
-
@Gąska said in The Official Status Thread:
@anonymous234 said in The Official Status Thread:
I hate how functional modern programming languages have become.
Did you mean: asynchronous?
Are they really asynchronous or does the syntax just hide a foreach loop?
Edit: Nevermind, I hate the async-or-bust mentality too. Every time HipsterWeb cries about my evil synchronous AJAX calls I say "shut the fuck up, it's my project and I know when it's safe to block for a microsecond or not!"
-
@Zenith said in The Official Status Thread:
@Gąska said in The Official Status Thread:
@anonymous234 said in The Official Status Thread:
I hate how functional modern programming languages have become.
Did you mean: asynchronous?
Are they really asynchronous or does the syntax just hide a foreach loop?
Another valid use of a callback. Either way, it's not necessarily a bad design. Maybe it is in
yourtheir specific case, butyouthey haven't provided enough details to establish that.Edit: Nevermind, I hate the async-or-bust mentality too.
The alternative is to write all code twice. I know it's not your problem that someone else has to work twice as hard while delivering zero useful features just so you can type ten characters less when calling the function, but seriously. It's not that big of an issue. And with async/await constructs, you don't even have to write down these callbacks - it's all done automatically for you.
Edit: didn't realize it was two different people.
-
@Gąska said in The Official Status Thread:
The alternative is to write all code twice. I know it's not your problem that someone else has to work twice as hard while delivering zero useful features just so you can type ten characters less when calling the function, but seriously. It's not that big of an issue. And with async/await constructs, you don't even have to write down these callbacks - it's all done automatically for you.
I'm not sure from how you phrased this if you like or hate asynchronous patterns.
When I do it in JavaScript, it turns into absolute spaghetti because I have to break program flow to return immediately, especially if I have to chain multiple calls. In a Windows desktop app, the mechanism is clumsy at best but the alternative to not pushing operations off the UI thread is to choke the UI so I tolerate it as best I can.
-
@Zenith said in The Official Status Thread:
@Gąska said in The Official Status Thread:
The alternative is to write all code twice. I know it's not your problem that someone else has to work twice as hard while delivering zero useful features just so you can type ten characters less when calling the function, but seriously. It's not that big of an issue. And with async/await constructs, you don't even have to write down these callbacks - it's all done automatically for you.
I'm not sure from how you phrased this if you like or hate asynchronous patterns.
I consider them necessary evil. Asynchronous FUNCTIONALITY is not just great but critically important in some use cases, in the sense that a lack of asynchronous variant of the given operation makes some things literally impossible. You can always use async API synchronously, but you can't do the opposite - so when deciding whether some API should be synchronous or asynchronous (assuming it's actually asynchronous, ie. waiting for external I/O), asynchronous should be chosen every single time.
When I do it in JavaScript, it turns into absolute spaghetti because I have to break program flow to return immediately, especially if I have to chain multiple calls.
As I said - JavaScript has async/await now. It's had for a few years. And if you're worried about compatibility, there are transpilers from new JS to old JS that take care of it for you. If you're using npm, they're very easy to set up (I think it's called babel? Should be easy enough to google up).
-
@Gąska said in The Official Status Thread:
Asynchronous FUNCTIONALITY is not just great but critically important in some use cases, in the sense that a lack of asynchronous variant of the given operation makes some things literally impossible.
You can always use async API synchronously, but you can't do the opposite - so when deciding whether some API should be synchronous or asynchronous (assuming it's actually asynchronous, ie. waiting for external I/O), asynchronous should be chosen every single time.
Uh, you spin off a thread and a synchronous operation becomes asynchronous. Synchronous to asynchronous turns into the JavaScript spaghetti I mentioned. Here's the (pseudocode) example I'm working from. It's from memory but I had code for one action I wanted to repeat. Not quite the same as chaining operations but close enough.
var L = new Array(); function DoSingularOperation (i) { var AJAX = new ActiveXObject("xmlhttp"); AJAX.async = false; AJAX.onsuccess = function(){L.add(i);}; AJAX.onfailure = function(){throw Exception("wtf: "+ i);} AJAX.send(); } function DoMultipleOperation (x) { for (i = 0 to x.length) { DoSingularOperation(x[i]);} } } function ButtonSingular() { try { DoSingularOperation(0); window.alert("Saved " + L.join(",")); } catch (e) {window.alert(e.Message);} } function ButtonMultiple() { try { DoMultipleOperation(GetSelectedItemsOrSomething()); window.alert("Saved " + L.join(",")); } catch (e) {window.alert(e.Message);} }
I don't do a ton of program logic in JavaScript. Even most of the work here is actually done in PHP. But it made sense here to update part of the UI without a postback. It's literally an AJAX call with an item number and an amount so I guess 200 bytes or something. I just needed to change the number of items in the cart or something without forcing a reload of the catalog that would've been slow, disorienting, and pointless. The complexity of this operation positively explodes if I have to multithread with exception handling (the onfailure event catches errors with the AJAX component, not the callbacks).
-
@Gąska Sorry I know I should've spun that off to another thread myself. Thanks for doing that. I wasn't trying to have an argument with you. I just find that my JavaScript explodes in complexity when I have to go async with callbacks. Functional programming is more of "in Soviet Russia..." thing for me. It's not incomprehensible but it's inside out to me with thinking procedurally.
-
@Zenith said in The Official Status Thread:
I wasn't trying to have an argument with you.
Okay, I'll find something else to do...
-
@Gąska said in The Official Status Thread:
@Zenith said in The Official Status Thread:
I wasn't trying to have an argument with you.
Okay, I'll find something else to do...
That's OK. When I say argument I usually mean fight. I don't have enough credibility to argue (persuade) that water puts out fires better than gasoline.
-
Status: working in progress.
Okay, okay…
Wish this program had more useful exporting options, so I wouldn’t have to reduce the working image’s size and colour space for internetty stuff and make sure I remember to undo both of those before saving again.
-
@kazitor said in The Official Status Thread:
Status: working in progress.
The is weak with this one.
-
@Gąska Care to reassess?
(damn, feels like it’s taken far longer than that. Time crawls when your warthogs change their load-bearing posture.)
-
@izzion
Status:
-
Status: Ibuprofen and bed. As I posted in another thread, I did some work in the yard "before it got too hot" this morning. And as expected, my body is expressing unhappiness with my having done that. I'm not sure if I'm going to be able to move in the morning. Also, I have a headache, for some probably unrelated reason.
-
@Zenith said in The Official Status Thread:
I just find that my JavaScript explodes in complexity when I have to go async with callbacks.
That sort of problem is where you want something that works a lot like a thread. It doesn't have to be a thread, it just has to have a way of suspending the operation of your function at some points and then resuming once some condition arises. Async/await is the mechanism for implementing this in JS nowadays, whereas it used to be done with promises (with much more overhead of complexity). Personally, I don't really like the way that they do this; I prefer the mechanisms of Lua and Tcl, as these give each coroutine its own stack and allow yielding from called functions without special syntax for the calling. This makes coroutines a bit heavier, but a lot easier to write; with a suitable library, your code ends up looking synchronous despite actually being asynchronous.
-
@dkf I’m on holiday and it’s too hot to think, so I’m just gonna throw out a dumb question that I should be able to answer myself if the brain worked:
What’s the difference again between stackful coroutines and green threads?
-
@topspin said in The Official Status Thread:
What’s the difference again between stackful coroutines and green threads?
Coroutines provide mechanisms for moving values into and out of them; yield and resume work a lot like return and call. There's also the ability to explicitly transfer control to another coroutine, effectively yielding the current one and resuming the other (which green threads could do, but usually don't). You can implement green threads on top of coroutines.
-
@Gąska said in The Official Status Thread:
Also also status: Just bought a new gaming monitor! 27 inches! 2560x1440! 144Hz! 1ms response time! Very performance! Wow!
So yeah, turns out I was scammed. Two weeks later (after I emailed them) they tell me they're out of stock and they never actually shipped anything, and are going to issue a refund.
-
status dry eyeballs are obnoxious. I thought it was something under my eyelid, but it seems to be more systemic.
Last night's sleep ~ ε