karthickgururaj
karthickgururaj on Hacker News
And if I wasn't clear - it wasn't my intent to treat this any less "useful". If anything, it is more interesting (for me) to read about solutions that give an intuitive feel, than dry analysis.
I'm not formally trained Mathematician, but I think this is not an analytic proof - it lacks rigour. It is more a graphical approach that appeals to the reader's intuition. I could be wrong here though.
Second, I really really thought the last graph will include y = x line and was very surprised to not see it :)
I just had one problem in reading it - the somewhat inconsistent use of fonts - often in the same line was not pleasant. The numeric zero ('0') in particular looks like character 'oh' ('o').
[0] https://nowiknow.com/the-marketing-stunt-that-vacuumed-up-a-...
It is not stupid - just counter-intuitive, which should give us a pause to think. You say, "A computer is a functioning machine first" - yes - but consider why SICP says, "Programs are meant to be read by humans and only incidentally for computers to execute." (see a discussion on the quote https://news.ycombinator.com/item?id=16431701).
(a) is easier to measure and optimize for. But it will select for students who will do well in later life - irrespective of what the univ has to offer. The univ's entrance criteria will exhibit this bias. Of course, some biases can be explicitly countered - by having a quota system for those with less privilege. But in each of those subsets, the univ still tries to maximize for absolute success of the individual.
(b) is harder to measure - as it seeks to quantify the portion of individual's success that can be attributed to the univ specifically.
There were couple of features that I missed - and needed to fire up a different viewer: 1. View PDF properties 2. Enter a slide-show mode, where a full page is shown and arrow keys advance (not scroll) the page.
Show HN: Garble displayed contents of gvim quickly
We at Vayavya Labs provide embedded software solutions across Automotive, EDA (Electronic Design Automation), Semiconductors, and Communications domains. We are looking for freelancers with a passion for reverse engineering, device driver development to be a part of a highly motivated team which works on Obsolescence Management of mission-critical embedded systems.
The lifetime of many mission-critical embedded systems is quite long and often requires replacement of the underlying hardware components (processor cards, network hardware, sensor cards etc..). Most often, the exact hardware component in the system would have gotten obsolete and would need to be replaced by similar hardware. Getting the same application software to run on the new hardware requires developing the device drivers for the new hardware as per the design of the older drivers. This often requires reverse-engineering the old driver code and/or binary patching.
Key Technical Skills:
* Strong in C and Data Structures
* Good understanding of x86 assembly language and x86 system architecture
* Experience in working with reverse engineering tools such as IDA pro, Ghidra
* Experience in binary patching
Key Non Technical traits: * Excellent problem-solving abilities
* Ability to learn and adapt
* Not afraid of failures, persistent and loads of patience
* Self-managed
Email: [email protected](Stan, fan, pan, man!) I'm an idiot, man!
So, now this is my own place.
And I didn't come here for all this.
This is one of my own…
I'm no different.
For now, the next generation's.
I'll be here for as long as there's anyone here.
Don't worry about it, I know.
[Hook, Solo]
Solo: So!
Bran: Why the…
So the rest is up to you guys. It's going to be a fun ride.
[Outro]
The entire world is watching me now (bark)
This is gonna be a fun ride.
[MUSIC]
Hey you guys
It's me, the one and only Jon Hamm!!!
You've got no idea who I'm, right?
But you know me, Jon!
I'm good! Now do you wanna bet? You don't wanna bet $50 that I'm really Jon Hamm!!!
Jon Hamm: What a great name!
If he were to say "Barry" (laugh)
I'd get a laugh! (laugh) That's Jon Hamm to ya!
Oh and that's not even the joke
It's not the funniest thing ever!
I know how to play, I know everything.
Here's a little secret
There
Some folks try with counters - but that very quickly gets out of hand. I try to prod them to a solution - by giving patterns that will defeat their solutions.
What I'm expecting is that the person can identify that use of stack here, which (and this is my source of confusion here) - is the most natural way to solve this problem. Push when we encounter an opening bracket, pop and match when we encounter a closing bracket. The function is generic, within 10 lines in C, can easily be extended to more bracket characters.
So - what is the point of this post?
Annapurna Devi: The Tragedy And Triumph Of Ravi Shankar’s First Wife
How about the following: It is easy to see that the last digit of x^5 is same as k^5, where k is the last digit of x. Then the problem reduces to proving that the ten possibilities, 0^5, 1^5, 2^5, ... 9^5 ends respectively in 0, 1, 2, ...9.
How India's think-tank iSpirt lost its true north (needs subscription)
I guess larger organisms are more likely to survive in this scenario. Maybe similar to the reasons why larger vehicles are more efficient for transportation: http://www.sustainablefreight.com.au/case-studies/bigger-is-...
But the question assumes(?) that the P language is meant for writing device drivers - and IMHO that assumption is not entirely true, for the language doesn't have any constructs for capturing the software's (the "physical device driver's" [1]) interaction with hardware.
For instance, I don't see a way to capture : 1. Software programmable registers (MMIO or over PCIe, I2C etc) 2. The software's contribution in DMA by setting up descriptors and buffers correctly and efficiently 3. Interrupts that the hardware can raise and how software should service them 4. Sequences to negotiate device capabilities and configuration, reset, perform transmit/receive, etc.
Many other comments here touch upon these and other aspects as being characteristic of "device drivers", they are missing altogether in the P language (I read the manual, didn't check the source, but I'm quite sure).
There is a "higher" driver - a logical device driver (LDD, [1]). An implementation of LDD is not specific to a device hardware (from some vendor); it remains same across all devices in a certain category. So an LDD is usually supplied/maintained by the OS vendor. For those who are aware of the WinCE architecture, the LDD is called an MDD ([2]).
The P language does seem to enable is specification of LDD - as long as it lends itself to the "message passing machines" paradigm (and in that respect, LDD is no more special to the P-language than any other software that can be modeled using "message passing machines").
References
[1] https://en.wikipedia.org/wiki/Device_driver - distinction between PDD and LDD