The project is split into several parts:
- The kernel driver, with simple 3D command forwarding and 3D resource allocation
- The userland driver, in fact the OpenGL backend
- The reference, explaining virtio-gpu commands
program firetest; | |
{ Classic fire animation using VGA mode 13h and colors 0 to 63... wee !!! } | |
uses Crt, VGA; | |
var i, heat: Integer; | |
quit: Boolean; | |
c: Char; |
The project is split into several parts:
# Wouldn't it be great if you could have STI like functionality | |
# without needing to encode strings of class names in the database? | |
# Well today is your lucky day! Discriminable Model is here to help. | |
# | |
# Simply specify your models desired type column, and provide a block to | |
# do the discrimination. If you want the whole STI-esque shebang of properly | |
# typed finder methods you can supply an array of 'discriminate_types' that will | |
# be used to apply an appropriate type. | |
# | |
# class MyModel < ActiveRecord::Base |
I was curious about [Chris McCord's Phoenix vs Rails article][original] -- if you haven't read it, go do that now first. Go ahead, this will still be here when you get back. It won't make much sense unless you've read the original.
Like many other Elixir enthusiasts, I come from a Ruby background. That said, I found Rails to be a curious choice for comparison to Phoenix, since Rails is really a kitchen-sink framework meant to handle everything from database migrations to asset-pipeline compilation. Sinatra, on the other hand, is a more
I've taken the benchmarks from Matthew Rothenberg's phoenix-showdown, updated Phoenix to 0.13.1 and ran the tests on the most powerful machines available at Rackspace.
Framework | Throughput (req/s) | Latency (ms) | Consistency (σ ms) |
---|
#!/usr/bin/env ruby | |
# usage: | |
# ruby generate.rb phrase wordfile | |
# | |
# example: | |
# ruby generate.rb "be a mean cat" words.txt | |
# => a act be name | |
# => a be cat name | |
# => a act bee man |