rexim

// cc `pkg-config --cflags openssl` -o simple_openssl_client simple_openssl_client.c  `pkg-config --libs openssl`

// Copyright 2021 Alexey Kutepov <reximkut@gmail.com>
//
// Permission is hereby granted, free of charge, to any person obtaining
// a copy of this software and associated documentation files (the
// "Software"), to deal in the Software without restriction, including
// without limitation the rights to use, copy, modify, merge, publish,
// distribute, sublicense, and/or sell copies of the Software, and to
// permit persons to whom the Software is furnished to do so, subject to

laat

sdb connect <ip>:<port> # connect to TV
sdb -s <deviceName> capability # get <installationPath>

# build
tizen cli-config "default.profiles.path=<profile_path>"
tizen build-web -out .buildResult -- <source-dir>
tizen package --type wgt --sign profileName -- <source-dir>/.buildResult # extract <package-file>
mv <package-file> .
rm -rf <source-dir>/.buildResult

joshnuss

# to run:
# > elixir --no-halt udp_server.exs
# to test:
# > echo "hello world" | nc -u -w0 localhost 2052
# > echo "quit" | nc -u -w0 localhost 2052

# Let's call our module "UDPServer"
defmodule UDPServer do
  # Our module is going to use the DSL (Domain Specific Language) for Gen(eric) Servers
  use GenServer

Diggsey

Looking into the Future

futures-rs is the library which will hopefully become a shared foundation for everything async in Rust. However it's already become renowned for having a steep learning curve, even for experienced Rustaceans.

I think one of the best ways to get comfortable with using a library is to look at how it works internally: often API design can seem bizarre or impenetrable and it's only when you put yourself in the shoes of the library author that you can really understand why it was designed that way.

In this post I'll try to put down on "paper" my understanding of how futures work and I'll aim to do it in a visual way. I'm going to assume you're already somewhat familiar with Rust and why futures are a useful tool to have at one's disposal.

For most of this post I'll be talking about how things work today (as of September 2017). At the end I'll touch on what's being proposed next and also make a case for some of the changes I'd like to see.

If you're interested in learning more ab

alexellis

Convert sequence of JPEG images to MP4 video

ffmpeg -r 24 -pattern_type glob -i '*.JPG' -i DSC_%04d.JPG -s hd1080 -vcodec libx264 timelapse.mp4

• -r 24 - output frame rate
• -pattern_type glob -i '*.JPG' - all JPG files in the current directory
• -i DSC_%04d.JPG - e.g. DSC_0397.JPG
• -s hd1080 - 1920x1080 resolution

Slower, better quality

Zodiase

'use strict';
class Abstract {
  // A static abstract method.
  static foo() {
    if (this === Abstract) {
      // Error Type 2. Abstract methods can not be called directly.
      throw new TypeError("Can not call static abstract method foo.");
    } else if (this.foo === Abstract.foo) {
      // Error Type 3. The child has not implemented this method.
      throw new TypeError("Please implement static abstract method foo.");

jonvaldes

use std::io;
use std::fs::File;
use std::io::Write;
use std::mem;
use std::slice;

#[derive(Clone)]
struct Color(u8, u8, u8);

struct Image {