It's 2024. You should use tsup instead of this.
🔥 Blazing fast builds
😇 CommonJS bundle
🌲 .mjs
bundle
✨ .d.ts
bundle + type-checking
It's 2024. You should use tsup instead of this.
🔥 Blazing fast builds
😇 CommonJS bundle
🌲 .mjs
bundle
✨ .d.ts
bundle + type-checking
// Copyright (c) 2020, the Dart project authors. Please see the AUTHORS file | |
// for details. All rights reserved. Use of this source code is governed by a | |
// BSD-style license that can be found in the LICENSE file. | |
// ============================================================================ | |
// Already existing definitions in dart:ffi. | |
// ============================================================================ | |
class NativeType { | |
const NativeType(); |
// struct XrApplicationInfo { | |
// char applicationName[128]; // 128 bytes | |
// uint32_t applicationVersion; // 4 bytes | |
// char engineName[128]; // 128 bytes | |
// uint32_t engineVersion; // 4 bytes | |
// XrVersion apiVersion; // assume this is a uint64_t, i.e. 8 bytes | |
// }; | |
class XrApplicationInfo extends Struct { | |
Pointer<Utf8> get applicationName => addressOf.cast<Utf8>(); |
$ clang -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/ test.c && ./a.out | |
int : 4 | |
unsigned int : 4 | |
long : 8 | |
unsigned long : 8 | |
size_t : 8 | |
ssize_t : 8 | |
off_t : 8 | |
wchar_t : 4 |
// | |
// main.m | |
// tbdswizzler | |
// | |
// Created by Steven Troughton-Smith on 10/12/2016. | |
// Copyright © 2016 High Caffeine Content. All rights reserved. | |
// | |
#import <Foundation/Foundation.h> |
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
"""Performs automatic speed edits to audio books. | |
Example usage: | |
Assuming you have an audiobook book.aax on your Desktop: | |
1. Convert it to wav: | |
ffmpeg -i ~/Desktop/book.aax ~/Desktop/book.wav | |
2. Adjust the speed: |
package main | |
import "fmt" | |
func main() { | |
fmt.Println("hello world") | |
} |
I did not submit this to Hacker News and did not intend that this post would have high circulation but have no real problem with it being there or with it having such. I have more recent comments below. This post is from January 2020 and predates the Modular Font Editor K (MFEK) project.
I have not worked on Rust projects in quite a while, and don't know if I ever will again. I feel many crate maintainers are way too perfectionist, for example, despite all the developer hours that went into this PR, it took the effort within years to be (halfway) merged.
There's always a reason not to merge, isn't there? It would be better done with a new nightly language feature, or the function signature should have a where clause, or the documentation is not perfect. There's always a new nit to pick in the world of Ru
I have a pet project I work on, every now and then. CNoEvil.
The concept is simple enough.
What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?