Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Avernar
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
181.
▲
by
Avernar
10y ago
Depends on the type of VM. A VM emulating the same type of processor just runs the client code direct on the processor. What stops the client code from messing with the reat of the system, which includes the VM supervisor code, is the pro
182.
▲
by
Avernar
10y ago
Minor nit pick: XT had one PIC, AT had two.
183.
▲
by
Avernar
10y ago
The bytes object is not a string type. It's treated more like a list of integers. It has very little string operations. Only in 3.5 did they add back the ability to % format. Not to mention all the b prefixes it just becomes painful
184.
▲
by
Avernar
10y ago
High quality unicode? Where every string with even a single emoji takes 4 times the memory. They should have used UTF-8 for their internal representation. Putting that aside, my issue with 3.X is that I have to use the unicode type even w
185.
▲
by
Avernar
10y ago
"Now, in Python 3, we finally have Unicode (utf-8) strings" This is not correct. Python strings are either ASCII, UCS-2 or UCS-4 depending on what code points they contain. Python 3 source code is by default UTF-8 and string lit
186.
▲
by
Avernar
10y ago
> I can see how this could reduce error, but I think this has more to do with cutting costs than adding efficiency to the ordering process. After using the touche screen at McDonalds only the first time was a little slower than going to
187.
▲
by
Avernar
10y ago
Ironic it works nice on desktop because it's glitchy on mobile. Had to reload several times before the wired banner would dock at the top of the screen. It would just float dead center of the screen the first few times.
188.
▲
by
Avernar
10y ago
The article title makes it sound like they're going against the FCC rules. The article itself however states they're complying the the FCC rules but are taking the more work for them option of just locking out the radio parameter
189.
▲
by
Avernar
10y ago
Seems that a good rant was what you needed. :D As I wrote in my other two posts tonight (more like morning, sigh) is that I tend to tune out emotional and aggressive writing styles. That's probably why my writing style tends to look a
190.
▲
by
Avernar
10y ago
> The AV software denied all disk I/O. If you have nowhere to put data, and no access to data, then you don't have a disk. You have a paperweight. AV software does not deny all disk IO. It just denies write access to a file ve
191.
▲
by
Avernar
10y ago
> Please consider dropping the adversarial attitude. A debate is by definition adversarial. I do tend to be more passionate when debating certain topics. If I've come across to you as aggressive I apologize. It's just my sty
192.
▲
by
Avernar
10y ago
> You should never be able to confuse an error message for anything else. Exactly. Which is why "Can't read file sensors.dat" is way better than just crashing. Crashing is one of the worst error messages you can get beca
193.
▲
by
Avernar
10y ago
Restarting quickly into a known state is not crashing. That is handling the error. How much of the program you restart is the question. Restart just a thread is better than restarting the whole program. But their app crashed. And hard.
194.
▲
by
Avernar
10y ago
> The easiest way to be sure a code path will run properly is to avoid writing it in the first place. Agreed. So the app shouldn't contain anything extra not related to it's primary function. However, handling error conditions
195.
▲
by
Avernar
10y ago
> In that scenario, your surgeon would see the program suddenly freeze. Only if the programmer or his management were incompetent. The display routine should be running on a separate thread than the processing code. No whole program fr
196.
▲
by
Avernar
10y ago
Yes it does! Showing "no telemetry available" is exactly what it should do. Crashing = unreliable. Reporting an error condition = reliable. Immediately? Took them 5 minutes to reboot the computer. The scan of the folder would
197.
▲
by
Avernar
10y ago
The disk did not fail. An I/O operation failed. The first is a permanent condition, the second can be permanent or transient. Big difference. In Linux a signal can cause an I/O to fail. In Windows it's antivirus and other
198.
▲
by
Avernar
10y ago
> When the disk is plugged back in, it should be able to restart without any problems. But I think that's a different kind of resiliency than what you're referring to. Yes and no. I was referring to restarting internally when
199.
▲
by
Avernar
10y ago
"Merge says the antivirus froze access to crucial data acquired during the heart catheterization. Unable to access real-time data, the app crashed spectacularly. The company claims that they included proper instructions in their docume
200.
▲
by
Avernar
10y ago
Massive amounts of homework is the perfect training for future work in North America. When kids get used to doing 60-80 hours worth of schoolwork for the same education that can be done in 40 hours they won't complain when their futur
201.
▲
by
Avernar
10y ago
I agree. Having a vehicle that requires me to take over in an emergency defeats the whole point of a driverless vehicle. I'd just rater drive myself then as I prefer to be a driver and not a passenger. Basically there should be two m
202.
▲
by
Avernar
10y ago
My friends and I play Clash Royal, Clash of Clans and Boom Beach. Out of the three it's Clash Royal that has made us come this close to smashing our tablets in rage. But it's not the IAP that's the cause. It's the skew
203.
▲
by
Avernar
11y ago
We're into semantics here. Portable requiring a CPU shim vs portable not requiring one. More complicated cpu/bus interfaces require the first one but if you can just use volatile for IO as done in embedded work you get much smal
204.
▲
by
Avernar
11y ago
If you do it correctly it should work. I'm curious if that code is running on a multi core (or even hyperthreaded) CPU.
205.
▲
by
Avernar
11y ago
Yes, you are correct that there are two issues. But solving 2 may solve 1 automatically or just need the compiler barrier intrinsics in the same spots as the processor barrier intrinsics. And yes, the first issue can be fixed with memory b
206.
▲
by
Avernar
11y ago
Why would you need to alias pointers for MMIO? There's one pointer to a struct that defines all your IO registers for that memory range.
207.
▲
by
Avernar
11y ago
Yes, you can use memory barriers for MMIO but you'd have to put them between every single statement that touches the MMIO address range. Not only will that bloat your code it would slow down access to all your regular variables as the
208.
▲
by
Avernar
11y ago
Volatile is for memory mapped IO. Some processors may need extra instuctions or configuration but that doesn't replace the need for volatile with MMIO. On x86 the MTTR/PAT mechanisms is what disables caching, write combining and
209.
▲
by
Avernar
11y ago
Wasn't me either. Can't downvote yet. :) Did some more research. Compilers have their own intrinsics that only affect the code generated (in addition to the processor ones). VS has _ReadBarrier, _WriteBarrier and _ReadWriteBarr
210.
▲
by
Avernar
11y ago
There are many types of barriers depending on the processor architecture. They're usually used in pairs so for example a read barrier would be used when mutex is acquired and the a write barrier when it's released. If the compiler
More ›