Seems like it has answers up to July 30, so he's either a time traveller or it's possible to get future answers by looking at the Wordle source.
1,572 karma · joined April 24, 2015
Seems like it has answers up to July 30, so he's either a time traveller or it's possible to get future answers by looking at the Wordle source.
With SQLite, it's often practical to issue several queries in situations where that would be too slow for a traditional client-server database.
> When the app starts, the managed DLLs are extracted and loaded in memory, avoiding the extraction to a folder.
https://learn.microsoft.com/en-us/dotnet/core/deploying/sing...
This kind of surprised me. Is that really a widespread assumption?
As an application developer I'm used to starting+committing transactions myself, outside the context of a stored procedure; I've done this with SQL Server and SQLite.
https://learn.microsoft.com/en-us/virtualization/windowscont...
App Installer has a nice UX on the happy path, but then you quickly discover that it will just fail for a non-negligible percent of customers.
IMO it's not a coincidence that very few first-party teams distribute their software using MSIX outside the Store. MSIX outside the store is broken, and for whatever reason the team responsible for it doesn't seem to be addressing that.
Haven't the responses already been handled? Assuming no time travel, it's not clear what actually happens after you edit a response header.
> If it's attractive, it will be expensive. That's how pricing works.
No. Prices are set by both supply and demand, and you're only considering demand.
Gotcha, true. I think you're doing yourself a disservice by including compile times (mostly out of your control) in your answer to "How long does each preview environment take to deploy?"
> Is there anything more specific you can share?
I would like to hear some technical details about the environment that each temporal app version gets deployed to. Like, is it a normal VM I can remote into? Docker containers? Something fancy like Firecracker micro-VMs?
You might not want to make all of those details public, but I need a bit more of an understanding of how a product works to consider using it.
Uhh... that's really slow. What is CodePreview doing to make it take that long? You could spin up a VM and copy a binary over to it much faster than that.
I'd love to see more tooling in this space (most people don't need Docker!) but I didn't get a sense of what CodePreview is actually doing from the homepage.
People who complain about offbeat-but-still-readable web design are killjoys who indirectly contribute to the sterility of the modern internet.
Scenario 2: less land dedicated to parking, people live closer together, commutes are shorter and can more often be done by bike/transit/walking
It's pretty clear which of those is better for the environment.
I don’t think building MSI installers is especially difficult; it’s kind of a set-it-and-forget-it thing. Configure Wix or Inno Setup once and then you’re good to go (on every Windows machine, no need to worry about multiple distros).
I also find it rewarding to maintain and develop the website. I started out small with a generic Hugo template, and over the years I've rewritten the whole thing one small commit at a time. It's been a good learning opportunity, and it's nice to have a low-stakes project where I can do anything I want. If I want to add a silly feature I just do it.
I have an 80lb greyhound in a not-very-large apartment and life is easy. Energy levels are more important than size (greyhounds sleep a lot) when it comes to apartment living for dogs.
ls | where modified > (date now) - 1hr
This was one of the biggest problems with Nu's dataframe functionality; it should be resolved now that we no longer ship with dataframes by default.
Totally agreed on dot method being nice for discoverability, that's something we need to do better on.
This is something we should communicate better in the docs, I'll see what I can do.
We also publish binaries: https://github.com/nushell/nushell/releases