# Init Published articles for Init. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Appwrite Init 2026 recap: Everything we shipped DevFeed: [Appwrite Init 2026 recap: Everything we shipped]() Original publisher: [Read original article]() Author: Aishwari Pahwa Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [releases](), [PostgreSQL](), [Amazon S3](), [Firewall](), [OAuth 2.0](), [Self-hosted]() Tags: [2](), [firewall](), [init](), [oauth2](), [postgresql](), [recap](), [release](), [releases](), [s3](), [self-hosted]() ### AI overview An Appwrite Init 2026 recap covering five days of launches, including Appwrite 2.0, a redesigned Console, native PostgreSQL, VectorsDB, DocumentsDB, MySQL, S3-compatible Storage, Firewall, OAuth2, and Domains. ### Source excerpt An Appwrite Init 2026 recap of all five days of launches, from Appwrite 2.0 and native PostgreSQL to VectorsDB, S3 support, Firewall, OAuth2, and Domains. ## Nativewind: Speeding up Styling in React Native DevFeed: [Nativewind: Speeding up Styling in React Native]() Original publisher: [Read original article]() Author: Jack Rosa Published: 2025-11-13T14:00:00Z Content type: tutorial Language: en Sources: [Hashrocket]() Topics: [React Native](), [Tailwind CSS](), [Mobile](), [Expo](), [Babel](), [Prettier]() Tags: [babel](), [css](), [init](), [install](), [mobile](), [react](), [react-native](), [tailwind](), [tailwind-css](), [tailwindcss]() ### AI overview A tutorial on using NativeWind to style React Native applications with Tailwind CSS classes. It explains NativeWind's runtime or Babel-plugin compile-time translation into React Native styles, and covers setup with Expo, Tailwind configuration, a global CSS file, and Babel. ### Source excerpt How Nativewind can speed up your React Native Development If you're anything like me, after working on a few web projects with Tailwind, it can feel like a drag to return to stacks that use other styling libraries. Tailwind has become, for myself, and many other developers, a standard styling paradigm. When starting my most recent React Native project, I was relieved to find out that NativeWind exists. NativeWind is exactly what is sounds like: Tailwind Classes in React Native. I can attest to the breeziness of writing an entire native app without a single call to StyleSheet.create. It's Familiar Nativewind takes the familiar classes of Tailwind CSS directly to your React Native components. Virtually every* class from Tailwind CSS can be used the exact same way on your mobile app (and the web), and the development results end up being faster iteration, less translating, and components that feel more readable and maintainable. Let's look at how to set it up NativeWind translates Tailwind class names into React Native styles at runtime or compile-time, if you use the Babel plugin. You end up with the the same composable mindset of Tailwind, but the output is just React Native styles. The setup is simple enough, for my latest project we used expo: npx expo install nativewind react-native-reanimated@~3.17.4 react-native-safe-area-context@5.4.0 npx expo install --dev tailwindcss@^3.4.17 prettier-plugin-tailwindcss@^0.5.11 Now to generate a tailwind config, run: npx tailwindcss init Be sure to include the path to your components in the generated tailwind.config.js file /** @type {import('tailwindcss').Config} */ module.exports = { content: ["./App.tsx", "./components/**/*.{js,jsx,ts,tsx}"], presets: [require("nativewind/preset")], theme: { extend: {}, }, plugins: [], } Next create your global.css file with tailwind's directives @tailwind base; @tailwind components; @tailwind utilities; Then, enable the Babel plugin in babel.config.js: module.exports = function (api) { api ## Multi-Module Projects with Cangjie DevFeed: [Multi-Module Projects with Cangjie]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-09-02T12:39:21Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [Package manager](), [modules](), [configuration](), [Code](), [Command-line interface]() Tags: [building](), [cangjie](), [cli](), [configuration](), [huawei](), [init](), [module](), [programming](), [run](), [structure]() ### AI overview A tutorial on using the Cangjie package manager, cjpm, to create and configure multi-module projects. It covers initializing a workspace, adding executable and library modules, registering them in the workspace configuration, adding source code, building, and running the project. ### Source excerpt The Cangjie package manager cjpm is a cli tool which can be used to setup multi-module projects. A module is simply a folder with a cjpm.toml file - whilst these can also be created by hand, the cli tool simplifies the process. The approach to the setup is to create a cjpm workspace at the project root and then separate module within the workspace. It will look like this: my-project (workspace) -- module-1 -- module-2 -- module-3Create the workspace In the root of your project, initialise a workspace: # create a project folder mkdir cat-pic-downloader cd cat-pic-downloader # initialise the workspace cjpm init --workspace At this stage, your project directory will have a cjpm.toml which is the configuration for your workspace. A newly initialised workspace config will look like this. [dependencies] [workspace] build-members = [] compile-option = "" link-option = "" members = [] target-dir = "" test-members = []Add the modules To add a module to the project, use the cjpm init command but with the options to specify the type of module to create (executable, a static library or a dynamic library). Let's add a couple of modules to our sample project. # create a static lib module called 'downloader' cjpm init --type=static --path downloader # create a static lib module called 'img-processor' cjpm init --type=static --path img_processor # create an executable module called 'runner' cjpm init --type=executable --path runner By default, a newly created module has a src directory and it's own cjpm.toml to configure the module. (Static library modules will have no source code. Executable modules will have a main.cj file.) Add the modules to the workspace So that the workspace is aware of the modules we created, we need to add them to the members field of the workspace's cjpm.toml. Edit the cjpm.toml as follows. [dependencies] [workspace] build-members = [] compile-option = "" link-option = "" members = ["./runner", "./downloader", "./img_processor"] target-dir = "" test-member ## New Default Code DevFeed: [New Default Code]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-03-06T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Boilerplate](), [Code](), [App](), [networking]() Tags: [app](), [code](), [developers](), [error-handling](), [errors](), [event](), [feature](), [github](), [init](), [network](), [networking](), [performance](), [toolbar]() ### AI overview Codename One changed the default boilerplate generated for new hello world apps. The update keeps the code in the init method and adds configurable defaults for two network threads, the global Toolbar, and generic network error handling. ### Source excerpt This is new behavior that went in without fanfare. If you created a new hello world app you might have noticed this. We changed the default boilerplate for Codename One and made it more representative of what you'd want to see in a hello world app. The entire change to the default generated app is within the init method: public void init(Object context) { // use two network threads instead of one updateNetworkThreadCount(2); __**(1)** theme = UIManager.initFirstTheme("/theme"); // Enable Toolbar on all Forms by default Toolbar.setGlobalToolbar(true); // Pro only feature Log.bindCrashProtection(true); addNetworkErrorListener(err -> { __**(2)** // prevent the event from propagating err.consume(); if(err.getError() != null) { Log.e(err.getError()); } Log.sendLogAsync(); Dialog.show("Connection Error", "There was a networking error in the connection to " + err.getConnectionRequest().getUrl(), "OK", null); }); } __1 By default networking in Codename One runs on one network thread for consistency. Two threads make more sense from a performance standpoint. We wanted to make this easily configurable and it should be easy in the init() method __2 Handling network errors in a generic way is probably one of the hardest things to grasp. So many developers are still stuck with the default error handling code... With that in mind we added a bit of boilerplate to handle network errors in a way that makes sense and should be easily customizable I had some thoughts about removing this boilerplate and packaging it in a class. But then I thought again. ## Loading large SQL Server CE databases on WP7 DevFeed: [Loading large SQL Server CE databases on WP7]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2011-11-15T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [sql-server](), [Databases](), [App]() Tags: [app](), [data](), [databases](), [file](), [init](), [issue](), [loading](), [parameter](), [query](), [sql-server]() ### AI overview This article explains how to load a large SQL Server Compact database from isolated storage in a Windows Phone 7 application. It describes the maximum database size error and shows how to add Max Database Size to the connection string. ### Source excerpt Recently I ran into an issue when trying to load the large database (approx. 50 mb) from isolated storage on WP7. Whenever I tried to query the Data Context, I got the following SqlCeException: The database file is larger than the configured maximum database size. This setting takes effect on the first concurrent database connection only. [ Required Max Database Size (in MB; 0 if unknown) = 0 ] After some searching over the web, I found this blog post covering some details of that parameter. The general work-around is adding 'Max Database Size' value (in megabytes) to the connection string, so it looks like: var connectionString = "Data Source='isostore:DB.sdf'; Max Database Size = 60"; Now your app should be able to init the data context. ## Magic SysRq - bezpieczny reset Linux'a DevFeed: [Magic SysRq - bezpieczny reset Linux'a]() Original publisher: [Read original article]() Author: Tom Published: 2011-09-17T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Linux](), [Kernel](), [ssh]() Tags: [fsck](), [init](), [kernel](), [linux](), [ssh](), [sync](), [timeout]() ### AI overview This Polish tutorial explains how Magic SysRq can help recover a severely unresponsive Linux system before performing a hard reset. It describes the reisub sequence--keyboard recovery, terminating processes, syncing disks, remounting filesystems read-only, and rebooting--and mentions remote-server use. ### Source excerpt Pomimo iż Linux uchodzi za stabilne środowisko to raz na jakiś czas trafi się ciężka zwiecha - z powodu przeciążenia, awarii sprzętu... nieistotne... Załóżmy że licho wzięło za cel główny serwer plików lub bazę danych dla wielu, wielu stron internetowych. Dostać się po ssh nie możemy bo lecą timeout'y, a siedząc bezpośrednio przy klawiaturze konsola nie reaguje. Mimo to coś ostro daje po dyskach, więc ewentualny twardy reset to na bank utrata części plików... jeśli system po nim w ogóle wstanie... 😑