TFA is arguing to use the router for navigation without having it push a separate URL to the bar, and still have back/forward work correctly. Essentially, creating a route change that isn't a route change, so it can properly trigger a router action. Of course, this is the actual point of `stateObject` as far as I understand it.
I think this is a good idea and would make a nice simple Backbone plugin. I've run into similar issues before; sometimes you want to display a temporary menu or other interstitial without a refresh taking you back to it.
Some purists get annoyed by this sort of thinking; they think that the URL bar should always reflect the current state of the app. I disagree with that line of thinking; different apps have different requirements and one size definitely does not fit all.
I've been writing Backbone applications for a while and I constantly run into router limitations that require creative solutions to get around. Backbone.routefilter is a great way to get some more flexibility - in every project I usually use a home-rolled combination of routefilter and a few more injected events. One of my favorites is to add permissions checking at the router definition level, to provide routes that only specific users should be able to use.
I've also been floating the idea around in my head of the url being essentially just a text representation of a state object - could easily just be a query string or something similar. Instead of a router globbing the url, you could attach event listeners to events on specific properties (similar to model/collection events), giving you all the power that most server-side routers have. For example:
That way, we can trigger routes exactly when we want them (with or without an actual url change), store private state using the History API, and support microstates. The best part (IMO) is that different routers can listen to separate parts of the url, allowing a URL change to trigger multiple routes on completely separate routers. This would go a long way toward true separation of concerns in larger apps.
Of course a lot more needs to be fleshed out. If any BB devs are interested in helping with idea, please let me know (email in profile)!
I think the GP was on the right track, but somewhat confused. They obviously don't do this on all models, but some dual-core models are disabled quad-cores. Remember the Athlon X3? That was a binned chip that usually was created from X4s with a broken core. Most buyers didn't mind, and some of them got lucky and were able to re-enable the disabled core.
It seems like the GP might be suggesting that a quad-core CPU will swap in another core when one dies. That doesn't happen. But the binning process allows them to still sell slightly defective silicon with disabled parts (cores, cache), which saves money.
On a related note, a lot of GPUs actually do have a few dozen execution units that are disabled by default and can be swapped in after stress testing at the factory. I believe some can even do that in the wild, but I could be wrong.
Oh whoops, I guess my VLSI professor lied to me. Maybe it only happens with certain multiprocessors. But yeah, there are definitely disabled cores in a lot of processors for the reasons you mentioned.
The cell processor had a main PowerPC core and eight floating-point SIMD co-processors called synergistic processing elements (SPE). For the PS3, one of the eight SPEs was disabled and another was reserved for the operating system, leaving the other six for developers.
Just use coinbase. IMO it's the only exchange that actually does fiat currency to BTC correctly - all the rest have horror stories posted all over bitcointalk and reddit.
You have to admit, that responding to a very informative message comparing and contracting Solaris's networking stack with Linux's with
Have you ever kissed a girl?
- Bryan
is incredibly tasteless.
But of course that was long ago.
I don't think it at all appropriate to criticize what was clearly an honest mistake with a call for his employer to fire him. I would expect that of the masses on Twitter and commenting on the PR, but not of Joyent or Cantrill.
The nicest description most Polygon staff could manage for the Xbox One's silhouette is "inoffensive" — there's no sugarcoating the console's lack of visual flair. Microsoft has created a system designed to blend into the other components of your home entertainment center, and it does that ... for better or worse.
It's quiet, and it runs relatively cool. But if you’re looking for subtlety, this is not the console for you.
Is it just me, or does the writer/editor not understand the word "subtle" here?
Otherwise, that was a really beautifully done review, at least visually.
"subtle - adjective 1. (esp. of a change or distinction) so delicate or precise as to be difficult to analyze or describe."
The xbox one is big, bulky, and not svelte.
This extends beyond the console dimensions, however. It has an external power brick, you can't stand it upright, and you can't stack another box on top of it due to the fan placement. Whereas the xbox one might camouflage better with your other AV boxes, the ps4 does a better job of subtly getting out of your way.
In my experience, it is absolutely worth having a degree - by all means, don't give that up, you should graduate, especially since you've come this far.
In terms of grades, I found that only my first two jobs cared about GPA - I took it off my resume shortly after because work experience became much more important. That's not to say you should give up on your GPA entirely, but in my experience companies care far less about GPA than they care about whether or not you can actually code.
I became a remote worker through a mix of bad luck, bad management, and a startup that wasn't going well. Of course at the time, I thought it was terrible; it turned out to be incredibly liberating and probably one the best things that's happened to me, professionally.
I was a software consultant for about a year and it was all networking - after all, that's how business gets done in the real world. I never had a time where I had too little work to do. My 'hack' for the whole thing was working in a coworking space, which is IMO the best ~$300/mo you can ever spend in a city that has one. I was lucky enough to have been working in one for more than a year and half before I started working for contract work, but I think you could easily do it in less time than that. When I started looking for work, everyone knew somebody; I never went outside of my space to find any work. It was incredibly convenient and really just worked out easily.
I always advise coders who are looking for freedom, a work environment change, or are newly unemployed to try a coworking space while they figure things out. You'll make a bunch of friends in a low-stress environment, meet entrepreneurs, and make great connections in the community that will get you work. It has worked well for those I know who have tried it - the secret is finding the right space. A socially-oriented space with as few walls as possible is best. You get used to the noise. Take long coffee breaks, go to lunch with people, go to happy hours and meetups. If you let it be known that you're looking for work and others know your skills, the jobs will come to you.
It gets worse - the UI team lead had an associate's degree in Art & Web Design from a community college, and a bachelor's in Zoology. [1] Normally, I would say credentials generally don't matter - but combined with the code quality, the argument writes itself.
I started looking him up after seeing this mention (and the awful code below). [2]
Really lame to attempt to name and shame someone by (ultimately) mocking their credentials and linking to code without context. Sure, some of that JS is bad, but I've seen much worse code that has been successfully deployed to solve problems.
Naming him wasn't the right approach and I apologize for that - however I cannot edit or delete the post. His involvement as the UI team lead is, however, public information. His credentials are not the main issue, of course.
There are serious quality issues along the entire codebase and a number of snippets that strongly suggest the team's primary skill is not JS. Given the cost and gravity of the project, I believe it is fair to say that the American public expects (and deserves) better. It speaks to the vast inefficiencies of the RFP process and gov IT contracting in general that code quality is so far down on the priority list.
It's not just aesthetic, either. There are serious functionality issues, as anybody who has used the site will attest to. And those bugs are not just limited to the backend. Backend bugs have seriously compromised the security of user accounts [1] and frontend bugs prevent major sections of the site from running at all [2].
It is one thing when ugly code is "successfully deployed to solve problems". It is quite another when ugly code on such a high-profile, expensive project is deployed to such disastrous effect.
The constructive part of the post is the repository I linked to (issues are being reported and fixed, for better or worse), and in bringing attention to the fact that government IT does not follow serious engineering practices. Serious attention needs to be brought to the problem so that it can be fixed. I am not happy about it, I am not pointing fingers with glee. I just hope that it has embarrassed HHS & the administration enough to make substantive change.
Oh god. Not only does [2] feature extremely creative uses of eval() (always a good sign), but also features the comment gem "create a new java date" in reference to a call to "new Date( ... )". Always nice to see nothing short of profound gulfs in understanding when it comes to our $9-digit technology initiatives...
The nice thing about Firefox is you can stop animated GIFs by hitting ESC. There is also an about:config setting that will turn them off as well. I personally find animated/video graphics annoying when trying to read.
So, if Adobe engineers eventually realized that they needed to upgrade their password security, and they had access to the passwords in their DB (they used 3DES, and they had the key) - why did they not immediately decrypt and hash all passwords?
I think this is a good idea and would make a nice simple Backbone plugin. I've run into similar issues before; sometimes you want to display a temporary menu or other interstitial without a refresh taking you back to it.
Some purists get annoyed by this sort of thinking; they think that the URL bar should always reflect the current state of the app. I disagree with that line of thinking; different apps have different requirements and one size definitely does not fit all.
I've been writing Backbone applications for a while and I constantly run into router limitations that require creative solutions to get around. Backbone.routefilter is a great way to get some more flexibility - in every project I usually use a home-rolled combination of routefilter and a few more injected events. One of my favorites is to add permissions checking at the router definition level, to provide routes that only specific users should be able to use.
I've also been floating the idea around in my head of the url being essentially just a text representation of a state object - could easily just be a query string or something similar. Instead of a router globbing the url, you could attach event listeners to events on specific properties (similar to model/collection events), giving you all the power that most server-side routers have. For example:
And so on.It would then be great to use the above microstates idea to create a navigation api like the following:
That way, we can trigger routes exactly when we want them (with or without an actual url change), store private state using the History API, and support microstates. The best part (IMO) is that different routers can listen to separate parts of the url, allowing a URL change to trigger multiple routes on completely separate routers. This would go a long way toward true separation of concerns in larger apps.Of course a lot more needs to be fleshed out. If any BB devs are interested in helping with idea, please let me know (email in profile)!