Yeah, with those old GS straight sticks, you really did force them to turn, pressing more forward and down on the inside edge, than a roll to the side. After reading your description, I'm excited to try the skiing on the balance board.
Knees suck. When they feel good, you should really try the new shaped skiis -- I'm sure you'll hate them at first, but once you get used to rolling instead of digging in, they are quite fun to ride. Carving is just so smooth.
With the "new" shaped skiis (more parabolic than hyperbolic) you roll them. It really is a matter of moving your mass from side to side, which puts the curved edge of the ski into the snow. Then you just ride in the direction of the curve.
Of course by forcing your feet, you can turn your skiis, but that requires much more energy.
That said, I've not used the balance board yet so I don't know how realistic the skiing/boarding is.
Think if you were Asus for a moment.. you build hardware, not software. Would it not be a smart business decision to out-source the software to a commercial company to support your hardware?
Sure you could hire developers to work on drivers and some thing, but your business is not a linux distro -- so you find a commercial vendor with a decent price-per-device and go with it.
We use these JVM options on a box with 16GB, and we could even increase the Xmx=12G to more and it would be fine, but we wanted to leave some room for disk cache.
That's a good point, but if you don't learn from history, then you are bound to repeat it. So bringing up past atrocities and publicly apologizing for them is a good thing. It's good for the organization doing the apologizing (so their members will learn about it) and it's good for society as a whole (so we collectively don't allow other atrocities to happen).
...is a neat idea. Besides the mentioned practice of raising and lowering pieces of code that the developers are happy and dissatisified with, hanging code encourages peer review.
Perhaps not in-depth code review, but physically hanging code in your office might "scare" developers into adhering to their organization's standards for fear of their coworkers mockery of poor code.
It might be difficult to hide shitty code when anyone can walk by and look at what *you* think is good. (At least it might take just as much effort to hide bad code as it does to make it good.)
Agreed. Why would I watch anything on the web in full screen? I'm surfing the web to slack it and randomly click links. I'm not making popcorn and sitting patiently for long clips to buffer.
I have been using ZODB for a couple years now and one thing that bothers me with systems that store objects directly instead of "dehydrated" representations of them is that when the underlying code for the object changes significantly all sort of weird things occur
But that may be just me. It is not just you. What you described is THE problem for all Object Oriented Database Management Systems.
That's why ORM (object-relational mapping) is so popular. People want a way to just use objects and not have to manually "dehydrate" data to disk. Unfortunately, most ORM isn't smart enough to execute the underlying SQL in an optimal way (depending of course on the relationship between your entities/objects).
For our 'users' table, we do table-level replication from the users database to each database that needs to join with 'users'. This limits us by only being able to read from the replicated table -- we require a separate connection to write to the 'users' table. (Other tables like 'user_preferences' and such may be replicated as necessary.)
Once the table is replicated, we simply join on user_id like we would if 'users' was native to our DB. We heavily foreign key off of user_id. This means deletes cannot be cascaded. Thus users cannot easily be deleted so we have statuses and types and such to define user roles and authorization.
Re:Who will advocate change?
on
Geekonomics
·
· Score: 2, Insightful
Heh, and how many people/companies are really replacing XP with Vista?
Re:Preventing malicious attacks
on
Geekonomics
·
· Score: 1
That money is better spent in court prosecuting the crackers. How does spending money in court better the society of which software is a foundation?
Just like disease makes immune systems stronger, attackers make [future generations of] software stronger.
Re:Software is under the eyes of regulators
on
Geekonomics
·
· Score: 1
Anyone know who regulates the software that controls traffic systems such as traffic lights or railroad crossings? Additionally, who regulates the software that controls municipality services such as electricity, natural gas, potable water, and waste water treatment?
Who will advocate change?
on
Geekonomics
·
· Score: 5, Interesting
The software vendors will know that their vacation from security is over. It would be nice if a book like this could change the software industry. But realistically, what industry will lobby their respective governments for this change? Obviously the established software companies will not advocate change. And, IMO, obviously the open-source community has little to gain with extra regulation and imposed cost on a Free and often voluntarily produced product.
I say the market itself will solve the problems with software security. New companies or new software products will only replace existing ones if the new ones are better. And like the book mentions, "better" is often measured in features. However, if enough damage is done with the current software flaws, some of the new features will include better security.
Example: Company A is sued by Customer B when Attacker C exploits a hole in Company A's software resulting in a financial loss for Customer B. Like the book mentions, Customer B usually has no legal grounds to sue. However, if this happens multiple times, Customer B may get wise and ensure proper contracts when entering new agreements.
These contracts could be required by customers when dealing with both closed source and open source companies. Buying a support contract from Sun for MySQL _could_ include certain software security requirements. And if Sun does not support this service, a business opportunity exists for another company.
Zone transfers are a very bad idea, especially incrementals... Why are zone transfers a bad idea? Why are incremental transfers a bad idea? If you manage a large zone, or support dynamic updates (probably with a low TTL), private incremental transfers between your nameservers are great.
I don't see the need for public zone transfers, unless for a specific reason. (Perhaps you play with voip and you need to publish certain resouce records for ITAD or SIP and you need to access your entire zone from anywhere.)
Some ccTLD registries require zone tranfers as part of the rules of owning a domain in that TLD. But they always give you an IP range to whitelist for a DNS zone transfer (AXFR).
I forgive you, your UID tells all. What? The parent's UID is only 100k more than yours -- you are practically neighbors on the UID scale.
Also, the parent only said "analog video for displaying computer output is obsolete" and mentioned nothing about signals.
I wouldn't say analog video is obsolete as new computer displays will probably support it for some time, but it sure is deprecated. The monitor the article describes can only utilize the maximum resolution of 2560 x 1600 via dual-link DVI-D.
Agreed. "Don't Make Me Think" has some simple examples too. I feel designers (from executive Product Management all the way to the end Developer and QA teams) should read it in order to think about the GUI in a slightly different way.
It's actually only a 5 day window. Which is easy for registrars to manage, but difficult for the registrant (domain owner). If you don't want the domain, you better email your registrar within 3 days of the registration. Also read the terms of service -- some registrars won't delete within the grace period. However, there are registrars (check out Moniker) that let you taste for a small fee (4 days for 25 cents I believe).
Slashdot Mirror
Correct. Good 800 and 888 numbers are valuable, same with SMS numbers (google = 466453).
Yeah, with those old GS straight sticks, you really did force them to turn, pressing more forward and down on the inside edge, than a roll to the side. After reading your description, I'm excited to try the skiing on the balance board.
Knees suck. When they feel good, you should really try the new shaped skiis -- I'm sure you'll hate them at first, but once you get used to rolling instead of digging in, they are quite fun to ride. Carving is just so smooth.
With the "new" shaped skiis (more parabolic than hyperbolic) you roll them. It really is a matter of moving your mass from side to side, which puts the curved edge of the ski into the snow. Then you just ride in the direction of the curve.
Of course by forcing your feet, you can turn your skiis, but that requires much more energy.
That said, I've not used the balance board yet so I don't know how realistic the skiing/boarding is.
Think if you were Asus for a moment.. you build hardware, not software. Would it not be a smart business decision to out-source the software to a commercial company to support your hardware?
Sure you could hire developers to work on drivers and some thing, but your business is not a linux distro -- so you find a commercial vendor with a decent price-per-device and go with it.
Just a thought.
We use these JVM options on a box with 16GB, and we could even increase the Xmx=12G to more and it would be fine, but we wanted to leave some room for disk cache.
JAVA_OPTS="-server -Xms3000m -Xmx12000m -Xss256k -XX:ThreadStackSize=256 -XX:-HeapDumpOnOutOfMemoryError -XX:-PrintGCDetails -XX:MaxPermSize=256m -XX:-PrintGCTimeStamps -Xloggc:/path-to-log-dir/gc.log -Dsun.net.inetaddr.ttl=10 -Dsun.net.inetaddr.negative.ttl=0 -Dsun.rmi.dgc.client.gcInterval=1800000 -Dsun.rmi.dgc.server.gcInterval=1800000"
Use the GC log option to watch it in action. You can safely ignore the DNS cache stuff, but I like to add it to every JVM to fix that major annoyance.
This is for Sun JDK 1.6 btw. We used different settings for JRockit.
That's a good point, but if you don't learn from history, then you are bound to repeat it. So bringing up past atrocities and publicly apologizing for them is a good thing. It's good for the organization doing the apologizing (so their members will learn about it) and it's good for society as a whole (so we collectively don't allow other atrocities to happen).
Unfortunately, Microsoft's strong-arm tactics of "encouraging" Windows on mobile devices (like the eeePC) are keeping them on top.
The "shrunken" PC and the "enlarged" mobile device will converge soon and that's where the market is at.
If linux can be on top in the growing mobile market, it will succeed. Otherwise, it will be an even longer battle.
What is the big deal here? It should be easy to retrieve "lost" email from Carnivore.
I don't like over-linking to wikipedia, but this image from Colorado Springs appears to be lightbulbs resting on the ground, powered remotely.
And this is from a movie, but in The Prestige, this same experiment appears to be shown.
Nikola Tesla performed a transmission of electrical energy without wires at his Colorado lab in the early 1900s.
Don't ask me how to do it though (:
You sure it was your computer?
...is a neat idea. Besides the mentioned practice of raising and lowering pieces of code that the developers are happy and dissatisified with, hanging code encourages peer review.
Perhaps not in-depth code review, but physically hanging code in your office might "scare" developers into adhering to their organization's standards for fear of their coworkers mockery of poor code.
It might be difficult to hide shitty code when anyone can walk by and look at what *you* think is good.
(At least it might take just as much effort to hide bad code as it does to make it good.)
Agreed. Why would I watch anything on the web in full screen? I'm surfing the web to slack it and randomly click links. I'm not making popcorn and sitting patiently for long clips to buffer.
But that may be just me. It is not just you. What you described is THE problem for all Object Oriented Database Management Systems.
That's why ORM (object-relational mapping) is so popular. People want a way to just use objects and not have to manually "dehydrate" data to disk. Unfortunately, most ORM isn't smart enough to execute the underlying SQL in an optimal way (depending of course on the relationship between your entities/objects).
For our 'users' table, we do table-level replication from the users database to each database that needs to join with 'users'. This limits us by only being able to read from the replicated table -- we require a separate connection to write to the 'users' table. (Other tables like 'user_preferences' and such may be replicated as necessary.)
Once the table is replicated, we simply join on user_id like we would if 'users' was native to our DB. We heavily foreign key off of user_id. This means deletes cannot be cascaded. Thus users cannot easily be deleted so we have statuses and types and such to define user roles and authorization.
What? Clearly, this will be the only domain name left: http://slackdaddy.org/node/1122
Heh, and how many people/companies are really replacing XP with Vista?
Just like disease makes immune systems stronger, attackers make [future generations of] software stronger.
Anyone know who regulates the software that controls traffic systems such as traffic lights or railroad crossings? Additionally, who regulates the software that controls municipality services such as electricity, natural gas, potable water, and waste water treatment?
I say the market itself will solve the problems with software security. New companies or new software products will only replace existing ones if the new ones are better. And like the book mentions, "better" is often measured in features. However, if enough damage is done with the current software flaws, some of the new features will include better security.
Example: Company A is sued by Customer B when Attacker C exploits a hole in Company A's software resulting in a financial loss for Customer B. Like the book mentions, Customer B usually has no legal grounds to sue. However, if this happens multiple times, Customer B may get wise and ensure proper contracts when entering new agreements.
These contracts could be required by customers when dealing with both closed source and open source companies. Buying a support contract from Sun for MySQL _could_ include certain software security requirements. And if Sun does not support this service, a business opportunity exists for another company.
JC Penny and other retailers probably stored the SSNs when their customers signed up for a branded credit card.
Is saving 10% on a few hundred dollar purchase really worth your financial identity?
I don't see the need for public zone transfers, unless for a specific reason. (Perhaps you play with voip and you need to publish certain resouce records for ITAD or SIP and you need to access your entire zone from anywhere.)
Some ccTLD registries require zone tranfers as part of the rules of owning a domain in that TLD. But they always give you an IP range to whitelist for a DNS zone transfer (AXFR).
Also, the parent only said "analog video for displaying computer output is obsolete" and mentioned nothing about signals.
I wouldn't say analog video is obsolete as new computer displays will probably support it for some time, but it sure is deprecated. The monitor the article describes can only utilize the maximum resolution of 2560 x 1600 via dual-link DVI-D.
A link to the 3007WFP model: http://accessories.us.dell.com/sna/products/Monitors/productdetail.aspx?c=us&l=en&s=dhs&cs=19&sku=222-7175
(see the 'note' at the right side of the page)
Agreed. "Don't Make Me Think" has some simple examples too. I feel designers (from executive Product Management all the way to the end Developer and QA teams) should read it in order to think about the GUI in a slightly different way.
It's actually only a 5 day window. Which is easy for registrars to manage, but difficult for the registrant (domain owner). If you don't want the domain, you better email your registrar within 3 days of the registration. Also read the terms of service -- some registrars won't delete within the grace period. However, there are registrars (check out Moniker) that let you taste for a small fee (4 days for 25 cents I believe).