My understanding is that LXDE does not support HiDPI very well because not everything is ported to gtk3. Do you have any experience to share with retina/3K/4K displays and LXDE?
721 karma · joined October 9, 2010
How is this possible? You carrier can activate your GPS chip? And then the GPS sends its coordinates to your carrier?
About the GPS: I didn't know it was possible to do this (is the signal transmitted to the carrier?).
They both describe all the parameters in the first sentence of the description.
They offer more bare services than AWS but they provide:
- Virtual Machines with many configurations available (on shared host or dedicated host)
- Private Cloud
- Private LAN with close to sub-millisecond latency
- Automated backup, snapshots
- API
- Load Balancer
- CDN (backed by Akamai)
- Block Storage (but I found it too slow for our needs)
- Different levels of managed hosting
LiquidWeb has even more options, but you usually need to pay for managed hosting (they throw in tons of free bandwidth though).
Support is really good: of course you sometimes end up speaking with someone who is clueless or overworked, but it is extremely rare and most support people are knowledgeable, helpful, and quick. We migrated a legacy VM with old cpanel and drupal sites and even though Drupal is not in their main expertise, they optimized the heck out of the configs and the sites are running twice as fast as before on weaker hardware.
Uptime is excellent: as opposed to Google or Amazon, they do everything in their power to keep the physical host and the VMs up and connected. In other words, they have a single host SLA (Amazon and Google's SLA only applies for multi-AZ outages if I remember correctly). They also built their own datacenters and are not collocating or renting someone else's datacenter.
Performance of their SSD VMs is better than Linode's and DO's VMs in our internal benchmarks.
If you need more than a few VMs, contacting Sales is a really good idea because they can make you some interesting offers.
The main downside for us is that they are located in central US so latency is not ideal for our eastern Canada customer base.
FWIW, we moved all our VMs from Linode to Storm because we lost confidence in Linode (DDOS, security, lack of transparency) even though the ratio performance/cost/reliability (in Newark, before the DDOS incident) was impossible to beat.
This is bad right? Like, worse than your hashed password and your mailing address.
The only good thing is that if I ever implement security questions, I'll remember Yahoo! and how it could end up in the wrong hands.
1. The floor is likely slippery.
2. It's dark
3. Glass mugs/Bottles can be broken and used as a weapon
4. There are hard table corners (watch out if you fall!)
5. There are chairs in the way (or maybe they can help you if you like to wield chairs!!)
A football team once picked a fight in a bar with a kung fu school. One of the best Kung Fu student slipped on the floor and his 15 years of kung fu went out of the window very very very quickly :-)
More seriously, a couple of observations:
1. Most styles of kung fu require dedicating years of practice before one can be called skilled. Compare this to Systema or Krav Maga where one can become a killer very quickly and you can expect people with little time to train to prefer these more modern martial arts. This says nothing about the depth of these martial arts, just the way they are organized and taught. As a concrete example: one of the first block I learned in Flying White Crane Kung Fu is actually very difficult to use in a street fight. Once you're good with it though, the opponent is in a very bad situation. With Krav Maga, the first block you may learn is usually very basic, very effective to block a punch, but you get less counter-attack possibilities.
2. Most of us do not need to fight for our life so of course, martial arts are waning as a whole.
3. MMA is very popular and most Kung Fu styles are not suitable for MMA: again it takes time to become an expert and many techniques cannot be used in a MMA ring (can I put my finger in your eye? what about using pressure points while you are tackling me on the floor? can you hit the neck with a spear hand?).
4. Kung Fu masters are usually very secretive and they sometimes die with most of their knowledge, especially if they do not find someone suitable to transfer that knowledge.
5. Finally, a sibling comment mentioned youtube. Many kung fu schools hesitate to use Youtube and when they do it, they usually do not show the best they are capable of. When I was training, I remember a master asking to only capture the movements of the upper body and hide the footwork :-)
1.7 was a very important release in the history of Django, just not a fun release to move to if you had a large codebase.
But you are right. At my previous job, I spent countless hours getting from 1.4 to 1.5, but the step from 1.5 to 1.6 was relatively painless.
Now the remaining part of your comment is unfair. Pure frontend is just one small part of webapp development: templating, controller, ORM, i18n, user and session management, security, testing, etc.
You can do a lot of web backend stuff without websocket. Django is ok for that and if you combine it with Django Rest Framework, you get powerful tools at your disposal.
I fear this whole story will be extremely bad for the kid and most news outlets should blame the newspaper instead of focusing on the kid or the bad science part.
[1] http://mobile.lemonde.fr/big-browser/article/2016/05/11/l-hi... [2] http://journalmetro.com/opinions/inspecteur-viral/962214/ce-...
I've been burned in the past by having to physically sign and scan or fax (!) contributor license agreements and I did not want to impose this additional hassle to potential contributors. Anybody has experience with this particular service or other alternatives?
Here is an example of a server application using Django REST Framework and the coreapi Python lib: https://github.com/core-api/heroku-game
- Save result as json, which is queryable in the database
- Save enough info in the task result to retry the task from the result.
- Retry a task from its result in Django Admin
- Run a periodic task now (e.g., to test your cron task)
[1] https://github.com/resulto-admin/django-celery-fulldbresult
We extended [2] django-celery db backend to store enough information about the periodic tasks to retry them directly in Django admin or to filter the results (we support storing the task results in JSON instead of pickle).
Celery is probably more difficult to configure but is far more flexible and robust than this lib...
[1] http://celery.readthedocs.org/en/latest/userguide/periodic-t... [2] https://github.com/resulto-admin/django-celery-fulldbresult
1. I can still use C-a with readline (go to first character)
2. If I ssh and then use screen, I can use C-a to navigate my remote screen and C-s to navigate my local tmux.
3. C-s is closer to C-a then other letters on my keyboard.
Even if your project is written in Swift, you can still use CocoaPods through bridging header, and you can use embedded frameworks for pure swift libraries (caveat: if you are targeting iOS 7, you need to copy and possibly modify the source of the frameworks you use because embedded frameworks are not supported in iOS7). Although Apple APIs are available with Swift, the documentation for some of the libraries still only provides examples in Obj-C.
My main issue right now is with the stability of XCode. SourceKit keeps crashing on me (every 30 minutes). It has become more stable with 6.1, but it used to crash when I had too many parameters in a function or when I was trying to mix Obj-C and Swift. Sometimes I get build errors and after a few calls to clean, I can build my app (go figure!). This makes developing in swift not as enjoyable as it could be.
1. The containers live on "your" VMs so you get the isolation of a virtual machine and do not worry about the other tenants' containers.
2. The VMs are part of a "private cloud", i.e., the internal network is not accessible by other tenants' VMs and containers.
#2 is what worried me the most in other container service offerings. It's easy to overlook protecting your internal ip when you manage VMs, it's even easier (and expected) when you deploy containers.
I totally agree that startup time of a container is far less than a VM, but I don't see how docker "removes all the trouble of running applications that you need for your development: databases, application servers, queues"
You still need to install, configure these services, make sure that the containers can talk to each other in a reliable and secure way, etc.
It's not just to keep things simple, it's to keep things consistent :-) Some NoSQL systems (e.g., MongoDB) introduced a new P in the equation (Performance) and used this to justify a lot of questionable decisions that affected consistency (and durability!). They have come a long way since these early decisions though.
If a system considers moderate latency as a partition, it would need to perform partition recovery on every write. That's why I'm not sure considering latency as partition is in line with the CAP theorem.
Maybe it is more related to availability though (not sure).
This sentence nailed what I thought was wrong with some early decisions in NoSQL systems: "because partitions are rare, there is little reason to forfeit C or A when the system is not partitioned."
If you are logged in Facebook, the facebook.com cookie is now first-party (because you visited facebook.com) and it is sent each time you make a request to Facebook from other domains. Blocking third party cookies usually mean that you block cookies from domain that you never directly visited (although Firefox has an option to disable ALL third-party cookies, even those from sites you visited [1]).
If the browser prevented sending cookies on cross-domain requests, it would block all authenticated cross-domain calls and that would severely limit the possible integration of web sites and applications. You could still pass session ids in the URL, but these can be sniffed by other servers, e.g., with the REFERER header.
[1] https://support.mozilla.org/en-US/kb/disable-third-party-coo...